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


- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 23 Oct 2026
- **Updated:** 24 Oct 2026
- **Also known as:** AZL-110777, BELL-CVE-2026-98964, DEBIAN-CVE-2026-98964, GHSA-8vjr-8rg3-pvjv, UBUNTU-CVE-2026-98964

## What is CVE-2026-98964?

CVE-2026-98964 is a high-severity vulnerability in Linux, published on 23 Oct 2026. 

### Official 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.

## Which versions are affected by CVE-2026-98964?


## How do I fix CVE-2026-98964?

Upgrade to a fixed version.

## Is CVE-2026-98964 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-98964 and fix it if it is affected.

What it is: CVE-2026-98964 is a high-severity vulnerability in Linux, published on 23 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-98964 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-2026-98964/ (Markdown: https://insights.sbomify.com/CVE-2026-98964/index.md)
```

## Sources

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

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