{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-74383 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-74383 is a high-severity vulnerability in Linux, published on 15 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-74383 and fix it if it is affected.\n\nWhat it is: CVE-2026-74383 is a high-severity vulnerability in Linux, published on 15 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-74383 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-74383/ (Markdown: https://insights.sbomify.com/CVE-2026-74383/index.md)","id":"CVE-2026-74383","markdown":"https://insights.sbomify.com/CVE-2026-74383/index.md","name":"CVE-2026-74383","record":{"aliases":["BELL-CVE-2026-74383","DEBIAN-CVE-2026-74383","GHSA-2x9w-pwqr-6m8q","UBUNTU-CVE-2026-74383"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Linux kernel NVMe driver","requires_auth":"none","summary":"A local attacker with NVMe hardware access can cause a kernel crash and denial of service on non-NUMA kernels due to an out-of-bounds array index.","user_interaction":"not_required","vuln_class":"null_dereference"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":8.4,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nnvme-pci: fix out-of-bounds access in nvme_setup_descriptor_pools\n\nnvme_setup_descriptor_pools() indexes dev-\u003edescriptor_pools[] using the\nnuma_node forwarded from hctx-\u003enuma_node by its single caller,\nnvme_init_hctx_common().  On a non-NUMA kernel hctx-\u003enuma_node is\nNUMA_NO_NODE (-1).  Because the parameter was declared 'unsigned', the\nvalue becomes UINT_MAX and the index walks off the array (sized to\nnr_node_ids), faulting during nvme_alloc_ns() and leaving the namespace\nwithout a /dev node.\n\nReproduces on any NVMe controller probed by a CONFIG_NUMA=n kernel:\n\n  BUG: unable to handle page fault for address: ffff889101603d38\n  RIP: 0010:nvme_init_hctx_common+0x5a/0x190 [nvme]\n  Call Trace:\n   nvme_init_hctx+0x10/0x20 [nvme]\n   nvme_alloc_ns+0x9e/0xa10 [nvme_core]\n   nvme_scan_ns+0x301/0x3b0 [nvme_core]\n   nvme_scan_ns_async+0x23/0x30 [nvme_core]\n\nSwitch the parameter to int and fall back to node 0 when it is\nNUMA_NO_NODE; node 0 is always present.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"nvme-pci: fix out-of-bounds access in nvme_setup_descriptor_pools","id":"CVE-2026-74383","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"nvme-multipath: fix flex array size in struct nvme_ns_head","id":"CVE-2026-74384"},"packages":[],"prev":{"headline":"net/sched: cls_bpf: prevent unbounded recursion in offload rollback","id":"CVE-2026-74382"},"products":["Linux"],"published":"2026-08-15","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-08-17","vendors":["Linux"]},"summary":"A local attacker with NVMe hardware access can cause a kernel crash and denial of service on non-NUMA kernels due to an out-of-bounds array index.","url":"https://insights.sbomify.com/CVE-2026-74383/"}