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

> A memory corruption vulnerability in the Linux kernel NVMe driver allows attackers to corrupt memory, potentially leading to code execution or system crashes.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 Dec 2025
- **Updated:** 15 Oct 2026
- **Also known as:** DEBIAN-CVE-2022-50756, GHSA-j2wx-wqf4-px3j, UBUNTU-CVE-2022-50756

## What is CVE-2022-50756?

CVE-2022-50756 is a high-severity memory corruption vulnerability in Linux, published on 24 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

## Which versions are affected by CVE-2022-50756?


## How do I fix CVE-2022-50756?

Apply the vendor's patch.

## Is CVE-2022-50756 being exploited?

There is no known exploitation of CVE-2022-50756 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-50756 and fix it if it is affected.

What it is: CVE-2022-50756 is a high-severity memory corruption vulnerability in Linux, published on 24 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-50756 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-50756/ (Markdown: https://insights.sbomify.com/CVE-2022-50756/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-50756
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-50756
- OSV: https://osv.dev/vulnerability/CVE-2022-50756

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-50756/
Summaries are generated and may contain mistakes; the official description above is the record.