CVE-2022-50314 json
nbd: Fix hung when signal interrupts nbd_start_device_ioctl()
published 2025-09-15 13 mo ago modified 2026-11-05 3 d ago also EUVD-2022-55541
- cvss
- 5.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 5%
- public exploits
- 0
- none known
Summary
In the Linux kernel, the following vulnerability has been resolved:
nbd: Fix hung when signal interrupts nbd_start_device_ioctl()
syzbot reported hung task [1]. The following program is a simplified version of the reproducer:
int main(void) { int sv[2], fd;
if (socketpair(AF_UNIX, SOCK_STREAM, 0, sv) < 0) return 1; if ((fd = open("/dev/nbd0", 0)) < 0) return 1; if (ioctl(fd, NBD_SET_SIZE_BLOCKS, 0x81) < 0) return 1; if (ioctl(fd, NBD_SET_SOCK, sv[0]) < 0) return 1; if (ioctl(fd, NBD_DO_IT) < 0) return 1; return 0; }
When signal interrupt nbd_start_device_ioctl() waiting the condition atomic_read(&config->recv_threads) == 0, the task can hung because it waits the completion of the inflight IOs.
This patch fixes the issue by clearing queue, not just shutdown, when signal interrupt nbd_start_device_ioctl().
Patch / fix
- Linux Linux 4.14.296, 4.19.262, 5.4.220, 5.10.150, 5.15.75, 5.19.17, 6.0.3, 6.1
- linux Debian 14, Debian 13, Debian 12 6.0.3-1
debian advisories DEBIAN-CVE-2022-50314
- linux Ubuntu 18.04 LTS 4.15.0-204.215
- linux Ubuntu 20.04 LTS 5.4.0-139.156
- linux Ubuntu 22.04 LTS 5.15.0-60.66
- linux-aws Ubuntu 18.04 LTS 4.15.0-1150.163
- linux-aws Ubuntu 20.04 LTS 5.4.0-1096.104
- linux-aws Ubuntu 22.04 LTS 5.15.0-1030.34
- linux-gcp Ubuntu 20.04 LTS 5.4.0-1100.109
- linux-gcp Ubuntu 22.04 LTS 5.15.0-1029.36
ubuntu advisories UBUNTU-CVE-2022-50314
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- git.kernel.org/stable/c/3ba3846cb3e2fb3c6fbf79e998472821b298419e commit
- git.kernel.org/stable/c/c7b4641bd2395c2f3cd3b0a0cbf292ed9d489398 commit
- git.kernel.org/stable/c/3575949513ea3b387b30dac1e69468a923c86caf commit
- git.kernel.org/stable/c/b2700f98b3f4dd19fb4315b70581e5caff89eb49 commit
- git.kernel.org/stable/c/c0d73be0af8c1310713bc39a8d7a22e35084e14f commit
- git.kernel.org/stable/c/62006a72b05e0d38727eef5188700f2488be5e89 commit
- git.kernel.org/stable/c/35fb7d4a53d9e36d1b91161ea9870d9c6d57dccf commit
- git.kernel.org/stable/c/1de7c3cf48fc41cd95adb12bd1ea9033a917798a commit
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2022-50314 updated cvss 4.4
kernel: nbd: Fix hung when signal interrupts nbd_start_device_ioctl()
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 moreaffected: no fix planned “Out of support scope”
-
Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 moreaffected: no fix available “Fix deferred”
-
Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 10 kernelnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 3 d ago
Exploit prediction
0.16% chance of exploitation in the next 30 days, higher than 5% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
Affected products
- Linux Linux
Classification
- Technology feeds
References
-
git.kernel.org
/stable/c/3ba3846cb3e2fb3c6fbf79e998472821b298419e
patch
-
git.kernel.org
/stable/c/c7b4641bd2395c2f3cd3b0a0cbf292ed9d489398
patch
-
git.kernel.org
/stable/c/3575949513ea3b387b30dac1e69468a923c86caf
patch
-
git.kernel.org
/stable/c/b2700f98b3f4dd19fb4315b70581e5caff89eb49
patch
-
git.kernel.org
/stable/c/c0d73be0af8c1310713bc39a8d7a22e35084e14f
patch
-
git.kernel.org
/stable/c/62006a72b05e0d38727eef5188700f2488be5e89
patch
-
git.kernel.org
/stable/c/35fb7d4a53d9e36d1b91161ea9870d9c6d57dccf
patch
-
git.kernel.org
/stable/c/1de7c3cf48fc41cd95adb12bd1ea9033a917798a
patch
Sources
- CVE List CVE-2022-50314
- NVD CVE-2022-50314
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.