Kernel memory corruption via sparse NUMA indexing
Published Aug 15, 2026 · Updated Aug 15, 2026
Out-of-bounds write in the Linux kernel allows attackers to corrupt kernel memory during NVMe namespace scanning on sparse-NUMA systems. The nvme_ns_head allocation sizes current_path by the count of possible NUMA nodes, but nvme_mpath_revalidate_paths indexes it with potentially sparse node IDs. Reachability requires NVMe multipath on a system with sparse NUMA node IDs; the public record demonstrates an out-of-bounds write but reports no attacker-controlled path or further consequence.
Summary
What happened
Out-of-bounds write in the Linux kernel allows attackers to corrupt kernel memory during NVMe namespace scanning on sparse-NUMA systems. The nvme_ns_head allocation sizes current_path by the count of possible NUMA nodes, but nvme_mpath_revalidate_paths indexes it with potentially sparse node IDs. Reachability requires NVMe multipath on a system with sparse NUMA node IDs; the public record demonstrates an out-of-bounds write but reports no attacker-controlled path or further consequence.
The record
- CVE
- CVE-2026-74384
- Published
- Aug 15, 2026
- Updated
- Aug 15, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Aug 15, 2026CVE publishedPublication date reported by the CVE source.
- Aug 15, 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=4.20
- Affected versionversion=f333444708f82c4a4d3ccac004da0bfd9cfdfa42 <001e57554de81aa79c25c18fd53911d8a415c304
- Affected versionversion=f333444708f82c4a4d3ccac004da0bfd9cfdfa42 <140d6fff4ed266592492a23444043842b4af7a62
- Affected versionversion=f333444708f82c4a4d3ccac004da0bfd9cfdfa42 <1d4131b5c9823c7d2c86389898ad1b466af7df5e
- Affected versionversion=f333444708f82c4a4d3ccac004da0bfd9cfdfa42 <316b5f1168264844aa125959de1d6da2b1905795
- Affected versionversion=f333444708f82c4a4d3ccac004da0bfd9cfdfa42 <7173a741fed73de6247384056fe92e582ba12507
- Affected versionversion=f333444708f82c4a4d3ccac004da0bfd9cfdfa42 <7e7b167e65610dfa7564d449474f4b477f9d4c1c
- Affected versionversion=f333444708f82c4a4d3ccac004da0bfd9cfdfa42 <9ffdd11bd6c961b46b3689850ff6c5d7af5c5fe5
- Affected versionversion=f333444708f82c4a4d3ccac004da0bfd9cfdfa42 <bde4d6eb53f7d3cdae7e62c9ee84345fdd6e70a6
What conditions does exploitation require?
What is affected?
Published CVSS scores
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.
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
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo