CVE-2026-98964EUVD-2026-108758GHSA-8VJR-8RG3-PVJV
nvmet: use the local P2P device on metadata allocation failure
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.10.273, 5.13, 6.6.160, 6.12.113, 6.18.57, and 1 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
Timeline
- CVE published
- First seen by cve.now
- Record last updated
Affected versions
- Linux Linux
From 5.10.43 · fixed in 5.10.273; From 5.12.10 · fixed in 5.13
- Linux Linux
5.13
- KernelLinux
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
References 8
git.kernel.org
- stable/c/eb72e2eeff559eb1eb07b1d644ce2bc1a16c4a80
- stable/c/48c8b59429d09a7c3598de425acbc2d3f4e6647b
- stable/c/e8f24ae4f45efe6861f801c6ebd2789c9016f1bc
- stable/c/3c231142c4f4bb96836469eb276026ec55940093
- stable/c/32f21607911a1f69c8f0f93a6c28fe6f8490aa98
- stable/c/ce79a6c5cc1b8054ec8d3eba16adda4a36113438
- stable/c/73bf0f9579633b531098a475e6e55c9316763aed
- stable/c/4aa9c0f377a4de5e8fddce76b34ee4529639a1ff