LiveActive security incident?Get immediate response
CVE Record

CVE-2022-50314: nbd: Fix hung when signal interrupts nbd_start_device_ioctl()

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

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue affects the Network Block Device driver. A local interaction with an NBD device can leave a kernel task hung, creating an availability problem. The sources do not show data theft, privilege escalation, or active exploitation. Business urgency is highest for systems that use or expose NBD devices.

Executive priority

Treat as a targeted availability risk. Patch through normal kernel maintenance, faster for systems using NBD in production storage paths. No source indicates emergency internet-scale exploitation.

Technical view

In nbd_start_device_ioctl(), a signal interruption while waiting for recv_threads to reach zero can leave the task waiting on in-flight I/O completion. The kernel fix clears the queue instead of only shutting it down. The CVE lists Linux kernel versions and stable commit references, but distro-specific affected package mapping is not provided.

Likely exposure

Linux systems using the nbd driver or exposing /dev/nbd* devices are the most relevant. Exposure is likely lower where NBD is not loaded, not used, or device access is tightly controlled. The source bundle does not identify specific distributions or cloud images.

Exploitation context

The report came from syzbot and describes a local hung-task reproducer using NBD ioctls. There is no KEV entry and no cited evidence of exploitation in the wild. Practical impact appears to be denial of service or operational disruption, not remote compromise.

Researcher notes

The CVE record is clear on root cause and fix behavior, but lacks CVSS, CWE, distro mapping, and privilege requirements. Avoid assuming remote reachability. Focus analysis on NBD device accessibility, kernel version lineage, and whether referenced stable commits are present.

Mitigation direction

  • Apply vendor kernel updates that include the referenced stable NBD fix.
  • Prioritize hosts using NBD-backed storage or automation around /dev/nbd* devices.
  • If patch status is unclear, check Linux distribution advisories for CVE-2022-50314.
  • Limit access to NBD device nodes according to normal operational requirements.

Validation and detection

  • Inventory systems with the nbd module loaded or NBD devices present.
  • Map running kernel versions to vendor advisories and stable commit inclusion.
  • Review logs for hung task reports involving nbd_start_device_ioctl or NBD.
  • Confirm patched kernels are installed and active after reboot.
Prepared
Confidence
medium
Sources
10

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2022-50314 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
9Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux5ea8d10802ec4c153a6e21eebaf412e2abd29736, 5ea8d10802ec4c153a6e21eebaf412e2abd29736, 5ea8d10802ec4c153a6e21eebaf412e2abd29736, 5ea8d10802ec4c153a6e21eebaf412e2abd29736, 5ea8d10802ec4c153a6e21eebaf412e2abd29736, 5ea8d10802ec4c153a6e21eebaf412e2abd29736, 5ea8d10802ec4c153a6e21eebaf412e2abd29736, 5ea8d10802ec4c153a6e21eebaf412e2abd29736unaffected
LinuxLinux4.12, 0, 4.14.296, 4.19.262, 5.4.220, 5.10.150, 5.15.75, 5.19.17, 6.0.3, 6.1affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.