LiveActive security incident?Get immediate response
CVE Record

CVE-2022-50756: nvme-pci: fix mempool alloc size

In the Linux kernel, the following vulnerability has been resolved: nvme-pci: fix mempool alloc size Convert the max size to bytes to match the units of the divisor that calculates the worst-case number of PRP entries. The result is used to determine how many PRP Lists are required. The code was previously rounding this to 1 list, but we can require 2 in the worst case. In that scenario, the driver would corrupt memory beyond the size provided by the mempool. While unlikely to occur (you'd need a 4MB in exactly 127 phys segments on a queue that doesn't support SGLs), this memory corruption has been observed by kfence.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2022-50756 is a Linux kernel NVMe PCI driver memory-corruption bug. It needs a narrow storage I/O condition to trigger, and the CVE text calls it unlikely. There is no CVSS score and no KEV listing in the provided sources, so business urgency is mainly for Linux systems with NVMe storage, especially high-throughput servers.

Executive priority

Treat as a targeted kernel maintenance item, not an emergency, unless critical Linux storage servers are exposed and lagging on kernel updates. Patch during the next appropriate maintenance window, with higher priority for NVMe-heavy infrastructure.

Technical view

The nvme-pci driver calculated PRP list mempool allocation using mismatched units. In a worst case, it could require two PRP lists while allocating for one, corrupting memory beyond the mempool. The source describes a specific 4MB, 127 physical segment case on queues without SGL support, observed by KFENCE.

Likely exposure

Exposure is most relevant to Linux systems using the nvme-pci driver with NVMe devices. The triggering conditions are narrow, and the affected-version data should be confirmed against kernel or distribution advisories before prioritizing broad fleet action.

Exploitation context

The provided sources do not state active exploitation, public exploit availability, or attacker prerequisites. The issue is documented as unlikely to occur and observed through KFENCE memory-corruption detection, not through reported real-world attacks.

Researcher notes

Do not assume exploitability beyond the source description. The CVE gives no CVSS, CWE, or exploitation evidence. Focus analysis on affected kernel branches, nvme-pci PRP list allocation behavior, queues without SGL support, and whether vendor backports include the stable commits.

Mitigation direction

  • Apply Linux kernel or distribution updates containing the referenced stable fixes.
  • Prioritize hosts using NVMe PCI storage and high-volume I/O workloads.
  • Check distribution advisories for exact affected and fixed kernel builds.
  • Reboot or live-patch according to your kernel vendor’s supported process.

Validation and detection

  • Inventory Linux hosts using NVMe PCI storage.
  • Compare running kernel builds against vendor advisories and stable fix commits.
  • Review kernel changelogs for the nvme-pci mempool allocation fix.
  • Monitor kernel logs or memory-safety tooling for related corruption reports.
Prepared
Confidence
medium
Sources
7

Public sources used

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-50756 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
0Timeline events
0ADP providers
6Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux943e942e6266f22babee5efeb00f8f672fbff5bd, 943e942e6266f22babee5efeb00f8f672fbff5bd, 943e942e6266f22babee5efeb00f8f672fbff5bd, 943e942e6266f22babee5efeb00f8f672fbff5bd, 943e942e6266f22babee5efeb00f8f672fbff5bdunaffected
LinuxLinux4.18, 0, 5.10.163, 5.15.87, 6.0.17, 6.1.3, 6.2affected
Weakness

CWE details

No CWE listed

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