# nvme-pci: fix mempool alloc size

CVE record · `CVE-2022-50756`

- **Identifiers:** `CVE-2022-50756`
- **State:** Confirmed
- **Severity:** CVSS 7.8 High
- **Critical:** No
- **CNA:** Linux
- **Technologies:** [Linux kernel](https://agentprime.io/advisories/technology/linux-kernel.md)
- **Published:** 24 Dec 2025
- **Updated:** 15 Oct 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: Linux) at 24 Dec 2025, 13:05 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it.

## Affected products, as the CNA wrote them

- Vendor: Linux. Product: Linux.
  - affected: `943e942e6266f22babee5efeb00f8f672fbff5bd to before dfb6d54893d544151e7f480bc44cfe7823f5ad23` (git)
  - affected: `943e942e6266f22babee5efeb00f8f672fbff5bd to before 9141144b37f30e3e7fa024bcfa0a13011e546ba9` (git)
  - affected: `943e942e6266f22babee5efeb00f8f672fbff5bd to before e1777b4286e526c58b4ee699344b0ad85aaf83a0` (git)
  - affected: `943e942e6266f22babee5efeb00f8f672fbff5bd to before b1814724e0d7162bdf4799f2d565381bc2251c63` (git)
  - affected: `943e942e6266f22babee5efeb00f8f672fbff5bd to before c89a529e823d51dd23c7ec0c047c7a454a428541` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `4.18`
  - unaffected: `before 4.18` (semver)
  - unaffected: `5.10.163 to 5.10.*, inclusive` (semver)
  - unaffected: `5.15.87 to 5.15.*, inclusive` (semver)
  - unaffected: `6.0.17 to 6.0.*, inclusive` (semver)
  - unaffected: `6.1.3 to 6.1.*, inclusive` (semver)
  - unaffected: `6.2 to *, inclusive` (original_commit_for_fix)
  - Other versions: affected

## Not analysed yet

We haven’t published our own analysis of this CVE. If a person reviews it, this page will say what’s affected and what has to be true for it to matter.

## Severity and exploitation

- 7.8 High, CVSS 3.1: `CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`, from CNA (Linux)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0020, the 10th percentile, on 19 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

This record came from the full history of the CVE Program, published 24 Dec 2025. New records show when each source confirmed them.

## Sources

- [CVE List: CVE-2022-50756](https://www.cve.org/CVERecord?id=CVE-2022-50756)
- [NVD: CVE-2022-50756](https://nvd.nist.gov/vuln/detail/CVE-2022-50756)

### References from the CNA

- <https://git.kernel.org/stable/c/dfb6d54893d544151e7f480bc44cfe7823f5ad23>
- <https://git.kernel.org/stable/c/9141144b37f30e3e7fa024bcfa0a13011e546ba9>
- <https://git.kernel.org/stable/c/e1777b4286e526c58b4ee699344b0ad85aaf83a0>
- <https://git.kernel.org/stable/c/b1814724e0d7162bdf4799f2d565381bc2251c63>
- <https://git.kernel.org/stable/c/c89a529e823d51dd23c7ec0c047c7a454a428541>

Facts on this page come from the CVE List as the CNA published them, with CVSS from the sources named above, CISA KEV and FIRST EPSS. Vendors, products and versions are shown as the CNA wrote them. We don’t reproduce the CVE’s description.

## Check whether this affects you

This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it. Compare the affected versions above with what you run.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), `get_advisory` returns this record and `search_advisories` finds related ones. Setup: <https://agentprime.io/mcp.md>
- As JSON: <https://api.agentprime.io/v1/advisories/CVE-2022-50756>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

The web page: <https://agentprime.io/advisories/CVE-2022-50756/>. Everything for agents: <https://agentprime.io/llms.txt>.
