CVE-2026-98964
Published Oct 23, 2026
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.
Is your site exposed to CVE-2026-98964?
Run a free security scan — no signup, results in seconds.
References
Other References
https://git.kernel.org/stable/c/32f21607911a1f69c8f0f93a6c28fe6f8490aa98
https://git.kernel.org/stable/c/3c231142c4f4bb96836469eb276026ec55940093
https://git.kernel.org/stable/c/4aa9c0f377a4de5e8fddce76b34ee4529639a1ff
https://git.kernel.org/stable/c/73bf0f9579633b531098a475e6e55c9316763aed
https://git.kernel.org/stable/c/ce79a6c5cc1b8054ec8d3eba16adda4a36113438
Frequently Asked Questions
What is CVE-2026-98964? +
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.
How do I check if I'm vulnerable to CVE-2026-98964? +
You can use Secably's free Website Scanner to check your website for known vulnerabilities. For infrastructure scanning, use the Port Scanner to identify exposed services that may be affected. Check the vendor advisories linked above for specific patch and version information.