CVE-2026-74384
Linux kernel nvme-multipath out-of-bounds write via sparse NUMA node IDs
Is CVE-2026-74384 being exploited?
Not confirmed. CVE-2026-74384 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.51% probability of exploitation in the next 30 days.
How severe is CVE-2026-74384?
CVE-2026-74384 is rated Critical with a CVSS score of 9.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-74384?
Yes. A fix has been recorded for CVE-2026-74384. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-74384 affect?
CVE-2026-74384 affects Linux kernel (nvme-core module), Systems with NVMe multipath enabled, PowerPC / NUMA-sparse architectures. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-74384?
Install kernel update containing the nvme_core fix or disable NVMe multipath on affected hosts.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
OOB kernel write leading to kernel crash (DoS) or potential local privilege escalation on systems with NVMe multipath and sparse NUMA IDs.
Patch when possible
- affected>= f333444708f82c4a4d3ccac004da0bfd9cfdfa42 and < 7e7b167e65610dfa7564d449474f4b477f9d4c1c
- affected>= f333444708f82c4a4d3ccac004da0bfd9cfdfa42 and < 316b5f1168264844aa125959de1d6da2b1905795
- affected>= f333444708f82c4a4d3ccac004da0bfd9cfdfa42 and < 1d4131b5c9823c7d2c86389898ad1b466af7df5e
- affected>= f333444708f82c4a4d3ccac004da0bfd9cfdfa42 and < 9ffdd11bd6c961b46b3689850ff6c5d7af5c5fe5
- affected>= f333444708f82c4a4d3ccac004da0bfd9cfdfa42 and < bde4d6eb53f7d3cdae7e62c9ee84345fdd6e70a6
- affected>= f333444708f82c4a4d3ccac004da0bfd9cfdfa42 and < 140d6fff4ed266592492a23444043842b4af7a62
- affected>= f333444708f82c4a4d3ccac004da0bfd9cfdfa42 and < 7173a741fed73de6247384056fe92e582ba12507
- affected>= f333444708f82c4a4d3ccac004da0bfd9cfdfa42 and < 001e57554de81aa79c25c18fd53911d8a415c304
- affected4.20
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.