{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-90412 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-90412 is a denial of service vulnerability in Linux, published on 17 Sep 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-90412 and fix it if it is affected.\n\nWhat it is: CVE-2026-90412 is a denial of service vulnerability in Linux, published on 17 Sep 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-90412 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-90412/ (Markdown: https://insights.sbomify.com/CVE-2026-90412/index.md)","id":"CVE-2026-90412","markdown":"https://insights.sbomify.com/CVE-2026-90412/index.md","name":"CVE-2026-90412","record":{"aliases":["BELL-CVE-2026-90412","DEBIAN-CVE-2026-90412","GHSA-c4vg-43j9-mh2m","UBUNTU-CVE-2026-90412"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel NVMe","requires_auth":"none","summary":"An attacker can cause NVMe host requests to fail silently by triggering memory allocation failures, leading to potential denial of service.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nnvmet: fix return status of RMI log page on allocation failure\n\nnvmet_execute_get_log_page_rmi() leaves 'status' holding NVME_SC_SUCCESS\n(set by the successful nvmet_req_find_ns() call) when the kzalloc() for\nthe log buffer fails. It then jumps to the out label and completes the\nrequest with a success status, so the host is told the command succeeded\nwhile no data was transferred.\n\nInitialize 'status' to NVME_SC_INTERNAL, matching the smart log handler,\nso an allocation failure is reported as an internal error.","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":"nvmet: fix return status of RMI log page on allocation failure","id":"CVE-2026-90412","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"IB/isert: reject login PDUs declaring more data than was received","id":"CVE-2026-90413"},"packages":[],"prev":{"headline":"nvme-fc: unmap cmd_iu DMA on rsp_iu mapping failure in init_request","id":"CVE-2026-90411"},"products":["Linux"],"published":"2026-09-17","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-19","vendors":["Linux"]},"summary":"An attacker can cause NVMe host requests to fail silently by triggering memory allocation failures, leading to potential denial of service.","url":"https://insights.sbomify.com/CVE-2026-90412/"}