Unspecified impact via incorrect P2P allocation cleanup
Published Oct 23, 2026 · Updated Oct 23, 2026
Incorrect cleanup in Linux 5.13 NVMe target allows attackers to cause unspecified impact via failed P2P metadata allocation. In drivers/nvme/target/core.c, nvmet_req_alloc_p2pmem_sgls() frees the data scatterlist using req->p2p_dev before assigning that device pointer. The path requires P2P-backed data allocation to succeed and metadata allocation to fail; published material does not establish attacker privileges or a specific security consequence.
Summary
What happened
Incorrect cleanup in Linux 5.13 NVMe target allows attackers to cause unspecified impact via failed P2P metadata allocation. In drivers/nvme/target/core.c, nvmet_req_alloc_p2pmem_sgls() frees the data scatterlist using req->p2p_dev before assigning that device pointer. The path requires P2P-backed data allocation to succeed and metadata allocation to fail; published material does not establish attacker privileges or a specific security consequence.
The record
- CVE
- CVE-2026-98964
- Published
- Oct 23, 2026
- Updated
- Oct 23, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Oct 23, 2026CVE publishedPublication date reported by the CVE source.
- Oct 23, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=5.10.43 <5.11
- Affected versionversion=5.12.10 <5.13
- Affected versionversion=5.13
- Affected versionversion=8a452d62e7cea3c8a2676a3b89a9118755a1a271
- Affected versionversion=bcd9a0797d73eeff659582f23277e7ab6e5f18f3 <32f21607911a1f69c8f0f93a6c28fe6f8490aa98
- Affected versionversion=bcd9a0797d73eeff659582f23277e7ab6e5f18f3 <3c231142c4f4bb96836469eb276026ec55940093
- Affected versionversion=bcd9a0797d73eeff659582f23277e7ab6e5f18f3 <4aa9c0f377a4de5e8fddce76b34ee4529639a1ff
- Affected versionversion=bcd9a0797d73eeff659582f23277e7ab6e5f18f3 <73bf0f9579633b531098a475e6e55c9316763aed
- Affected versionversion=bcd9a0797d73eeff659582f23277e7ab6e5f18f3 <ce79a6c5cc1b8054ec8d3eba16adda4a36113438
- Affected versionversion=c440cd080761b18a52cac20f2a42e5da1e3995af
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Contact us