In the Linux kernel, the following vulnerability has been resolved: nvmet: use the local P2P device on metadata allocation failure nvme…
CVE-2026-98964 · GHSA-8vjr-8rg3-pvjv · EUVD-2026-108758 · published 23 Oct 2026
How serious is it
- Severity: high, CVSS score 7.5 out of 10.
- No exploit prediction (EPSS) score yet.
- Not on the CISA list of exploited vulnerabilities.
- No public exploit in Exploit-DB.
Is your app affected by CVE-2026-98964?
Paste this prompt into Claude Code, Cursor or any AI coding tool: it runs a free Shippable scan of your project and fixes what it finds. Built with Lovable, Bolt or v0? Scan your live app. Or upload your package file.
Who is affected
- Linux Linux: 5.10.43 <5.11
- Linux Linux: bcd9a0797d73eeff659582f23277e7ab6e5f18f3 <32f21607911a1f69c8f0f93a6c28fe6f8490aa98
- Linux Linux: bcd9a0797d73eeff659582f23277e7ab6e5f18f3 <73bf0f9579633b531098a475e6e55c9316763aed
- Linux Linux: bcd9a0797d73eeff659582f23277e7ab6e5f18f3 <3c231142c4f4bb96836469eb276026ec55940093
- Linux Linux: patch: 6.12.113
- Linux Linux: 5.12.10 <5.13
- Linux Linux: c440cd080761b18a52cac20f2a42e5da1e3995af
- Linux Linux: patch: 0
- Linux Linux: patch: 7.3
- Linux Linux: bcd9a0797d73eeff659582f23277e7ab6e5f18f3 <4aa9c0f377a4de5e8fddce76b34ee4529639a1ff
How to check
- Find out whether you run the affected product and which version, then compare it with the versions above.
How to fix
Copies a prompt for Claude Code, Cursor or Codex that asks it to check whether you run this product.
- Apply the vendor's update or mitigation from the references below. If there is none yet, limit exposure of the affected service until there is.
- If a vulnerable version was live, check your logs and rotate the secrets that server could read.
The advisory
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.
Check your whole app
Dependencies are only half of it. Free and read-only: before you push, run npx shippable-dev scan localhost:3000 in your project folder, no account needed. For your live app, you prove it's yours with a one-line tag first.
References
- git.kernel.org/stable/c/3c231142c4f4bb96836469eb276026ec55940093
- git.kernel.org/stable/c/32f21607911a1f69c8f0f93a6c28fe6f8490aa98
- git.kernel.org/stable/c/ce79a6c5cc1b8054ec8d3eba16adda4a36113438
- git.kernel.org/stable/c/73bf0f9579633b531098a475e6e55c9316763aed
- git.kernel.org/stable/c/4aa9c0f377a4de5e8fddce76b34ee4529639a1ff
- nvd.nist.gov/vuln/detail/CVE-2026-98964
Merged from ENISA EUVD. Last updated 25 Oct 2026. All vulnerabilities · RSS · JSON