CVE-2025-40080

nbd: restrict sockets to TCP and UDP

N/A

Published: October 28, 2025 at 11:48 AM UTC

Updated: October 19, 2026 at 09:10 PM UTC

4 products affected across 2 vendorsLinux KernelSIMATIC S7-1500 CPU 1518-4 Pn /dp MFP FirmwareSiplus S7-1500 CPU 1518-4 Pn /dp MFP Firmware

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

N/A

Exploit prediction

EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: nbd: restrict sockets to TCP and UDP Recently, syzbot started to abuse NBD with all kinds of sockets. Commit cf1b2326b734 ("nbd: verify socket is supported during setup") made sure the socket supported a shutdown() method. Explicitely accept TCP and UNIX stream sockets.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Linux Kernel · Linux

90%

083322455c67d278c56a66b73f1221f004ee600a4.14.152 4.19.824df728651b8a99693c69962d8e5a5b9e5a3bbcc74fa1cbd587ef967812f9d9f6ce46ec1dead7502c5.3.9 5.483322455c67d278c56a66b73f1221f4ee600acf1b2326b734896734c6e167e41766f9cee7686a

Vendor states this is fixed in 37ad11f20e164c23ce827dd455b42c0fdd29685c (fixed)

Vendor states this is fixed in 4f9e6ff6319dbcebea64b50af0304cf0ad7e97e7 (fixed)

Vendor states this is fixed in 808e2335bc1cf2293b9e36ccc94c267c81509c71 (fixed)

Vendor states this is fixed in 9f7c02e031570e8291a63162c6c046dc15ff85b0 (fixed)

Vendor states this is fixed in c365e8f20f4201d873a70385bd919f0fb531e960 (fixed)

Affected range stops below 4.15, so it looks safe — our inference, not a vendor statement

Affected range stops below 4.20, so it looks safe — our inference, not a vendor statement

Vendor states this is fixed in 5.4 (unaffected)

Vendor states this is fixed in 6.1.156 (unaffected)

Vendor states this is fixed in 6.12.53 (unaffected)

Vendor states this is fixed in 6.17.3 (unaffected)

Vendor states this is fixed in 6.18 (unaffected)