{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-74361 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-74361 is a critical vulnerability in Linux, published on 15 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-74361 and fix it if it is affected.\n\nWhat it is: CVE-2026-74361 is a critical vulnerability in Linux, published on 15 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-74361 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-74361/ (Markdown: https://insights.sbomify.com/CVE-2026-74361/index.md)","id":"CVE-2026-74361","markdown":"https://insights.sbomify.com/CVE-2026-74361/index.md","name":"CVE-2026-74361","record":{"aliases":["BELL-CVE-2026-74361","DEBIAN-CVE-2026-74361","GHSA-597p-qxfw-c3vg","UBUNTU-CVE-2026-74361"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["other"],"network_reachable":"yes","non_default_config":false,"product_category":"Linux kernel NVMe","requires_auth":"none","summary":"An off-by-one error in the NVMe FDP bounds check allows invalid index usage, potentially leading to undefined behavior or memory access issues.","user_interaction":"not_required","vuln_class":"integer_overflow"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":9.8,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/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: fix FDP fdpcidx bounds check\n\nThe fdpcidx bounds check sets n = NUMFDPC + 1 but used \u003e instead of \u003e=,\nincorrectly accepting fdp_idx when it equals n (i.e. NUMFDPC + 1).","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: fix FDP fdpcidx bounds check","id":"CVE-2026-74361","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"integer_overflow","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"ext2: fix ignored return value of generic_write_sync()","id":"CVE-2026-74362"},"packages":[],"prev":{"headline":"bpf: Reject exclusive maps for bpf_map_elem iterators","id":"CVE-2026-74360"},"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":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-10-16","vendors":["Linux"]},"summary":"An off-by-one error in the NVMe FDP bounds check allows invalid index usage, potentially leading to undefined behavior or memory access issues.","url":"https://insights.sbomify.com/CVE-2026-74361/"}