nvme-pci: fix mempool alloc size
- 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.163, 5.15.87, 6.0.17, 6.1.3
- 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
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
In the Linux kernel, the following vulnerability has been resolved: nvme-pci: fix mempool alloc size Convert the max size to bytes to match the units of the divisor that calculates the worst-case number of PRP entries. The result is used to determine how many PRP Lists are required. The code was previously rounding this to 1 list, but we can require 2 in the worst case. In that scenario, the driver would corrupt memory beyond the size provided by the mempool. While unlikely to occur (you'd need a 4MB in exactly 127 phys segments on a queue that doesn't support SGLs), this memory corruption has been observed by kfence.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Linux Linux
From 943e942e6266f22babee5efeb00f8f672fbff5bd · fixed in dfb6d54893d544151e7f480bc44cfe7823f5ad23; From 943e942e6266f22babee5efeb00f8f672fbff5bd · fixed in 9141144b37f30e3e7fa024bcfa0a13011e546ba9; From 943e942e6266f22babee5efeb00f8f672fbff5bd · fixed in e1777b4286e526c58b4ee699344b0ad85aaf83a0; From 943e942e6266f22babee5efeb00f8f672fbff5bd · fixed in b1814724e0d7162bdf4799f2d565381bc2251c63; From 943e942e6266f22babee5efeb00f8f672fbff5bd · fixed in c89a529e823d51dd23c7ec0c047c7a454a428541
- Linux Linux
4.18
- KernelLinux
From 4.18.0 · fixed in 5.10.163; From 5.11.0 · fixed in 5.15.87; From 5.16.0 · fixed in 6.0.17; From 6.1.0 · fixed in 6.1.3