CVE-2026-74383
Last modified
CVE-2026-74383 is a high-severity vulnerability rated 8.4/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: nvme-pci: fix out-of-bounds access in nvme_setup_descriptor_pools nvme_setup_descriptor_pools() indexes dev->descriptor_pools[] using the numa_node forwarded from hctx->numa_node by its single caller, nvme_init_hctx_common(). On a non-NUMA kernel hctx->numa_node is NUMA_NO_NODE (-1). EPSS estimates a 0.17% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: nvme-pci: fix out-of-bounds access in nvme_setup_descriptor_pools nvme_setup_descriptor_pools() indexes dev->descriptor_pools[] using the numa_node forwarded from hctx->numa_node by its single caller, nvme_init_hctx_common(). On a non-NUMA kernel hctx->numa_node is NUMA_NO_NODE (-1). Because the parameter was declared 'unsigned', the value becomes UINT_MAX and the index walks off the array (sized to nr_node_ids), faulting during nvme_alloc_ns() and leaving the namespace without a /dev node. Reproduces on any NVMe controller probed by a CONFIG_NUMA=n kernel: BUG: unable to handle page fault for address: ffff889101603d38 RIP: 0010:nvme_init_hctx_common+0x5a/0x190 [nvme] Call Trace: nvme_init_hctx+0x10/0x20 [nvme] nvme_alloc_ns+0x9e/0xa10 [nvme_core] nvme_scan_ns+0x301/0x3b0 [nvme_core] nvme_scan_ns_async+0x23/0x30 [nvme_core] Switch the parameter to int and fall back to node 0 when it is NUMA_NO_NODE; node 0 is always present.
Metrics
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= d977506f8863807129d7a11f4057dfb1b38085ea, < 3e8aed5edaeeb237f97255d711aac6b5843fc059; >= d977506f8863807129d7a11f4057dfb1b38085ea, < fa9b6accd1ad7af6914b409c6b003c417724c299; >= d977506f8863807129d7a11f4057dfb1b38085ea, < a192b8cfa447e1b3701a13434a31c392b2e7ed29 |
| Linux | Linux | 6.16 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-74383?
How severe is CVE-2026-74383?
How do I fix CVE-2026-74383?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-74377In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-74378In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-74379In the Linux kernel, the following vulnerability has been re…
- CVE-2026-74380In the Linux kernel, the following vulnerability has been re…8.8
- CVE-2026-74381In the Linux kernel, the following vulnerability has been re…
- CVE-2026-74382In the Linux kernel, the following vulnerability has been re…
- CVE-2026-74384In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-74385In the Linux kernel, the following vulnerability has been re…7.5
- CVE-2026-74386In the Linux kernel, the following vulnerability has been re…
- CVE-2026-74387In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-74388In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-74389In the Linux kernel, the following vulnerability has been re…
Are you affected by CVE-2026-74383?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
