Skip to content
TrackCVE
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API documentationPage
  • MCP serverPage
  • Data sourcesPage
  • ChangelogPage
  • AboutPage
  • How it's builtPage
Back

CVE-2022-50314

nbd: Fix hung when signal interrupts nbd_start_device_ioctl()

Medium5.5EPSS 0.16%
Published
Updated
Reserved
Assigned by
Linux

Description

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().

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 14 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2022-50314, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.16% · top 95% of all CVEs (7 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected 5ea8d10802ec4c153a6e21eebaf412e2abd29736 – < 3ba3846cb3e2fb3c6fbf79e998472821b298419e
    • affected 5ea8d10802ec4c153a6e21eebaf412e2abd29736 – < c7b4641bd2395c2f3cd3b0a0cbf292ed9d489398
    • affected 5ea8d10802ec4c153a6e21eebaf412e2abd29736 – < 3575949513ea3b387b30dac1e69468a923c86caf
    • affected 5ea8d10802ec4c153a6e21eebaf412e2abd29736 – < b2700f98b3f4dd19fb4315b70581e5caff89eb49
    • affected 5ea8d10802ec4c153a6e21eebaf412e2abd29736 – < c0d73be0af8c1310713bc39a8d7a22e35084e14f
    • affected 5ea8d10802ec4c153a6e21eebaf412e2abd29736 – < 62006a72b05e0d38727eef5188700f2488be5e89
    • affected 5ea8d10802ec4c153a6e21eebaf412e2abd29736 – < 35fb7d4a53d9e36d1b91161ea9870d9c6d57dccf
    • affected 5ea8d10802ec4c153a6e21eebaf412e2abd29736 – < 1de7c3cf48fc41cd95adb12bd1ea9033a917798a
  • Linux · Linux

    • affected 4.12
    • unaffected < 4.12
    • unaffected 4.14.296 – ≤ 4.14.*
    • unaffected 4.19.262 – ≤ 4.19.*
    • unaffected 5.4.220 – ≤ 5.4.*
    • unaffected 5.10.150 – ≤ 5.10.*
    • unaffected 5.15.75 – ≤ 5.15.*
    • unaffected 5.19.17 – ≤ 5.19.*
    • unaffected 6.0.3 – ≤ 6.0.*
    • unaffected 6.1 – ≤ *

References (8)

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2022-50314 badge
[![CVE-2022-50314](https://trackcve.app/badge/CVE-2022-50314.svg)](https://trackcve.app/cve/CVE-2022-50314)

Record last updated .