{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-89612 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-89612 is a critical vulnerability in Linux, published on 11 Sep 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-89612 and fix it if it is affected.\n\nWhat it is: CVE-2026-89612 is a critical vulnerability in Linux, published on 11 Sep 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-89612 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-89612/ (Markdown: https://insights.sbomify.com/CVE-2026-89612/index.md)","id":"CVE-2026-89612","markdown":"https://insights.sbomify.com/CVE-2026-89612/index.md","name":"CVE-2026-89612","record":{"aliases":["DEBIAN-CVE-2026-89612","GHSA-v9qj-wpxr-47gc","UBUNTU-CVE-2026-89612"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Linux kernel NTFS","requires_auth":"none","summary":"A crafted NTFS image can cause an integer overflow leading to out-of-bounds memory access, potentially crashing the system.","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\nntfs: reject invalid MFT LCNs from boot sector\n\nThe NTFS boot sector stores the MFT and MFTMirr locations as unsigned\n64-bit LCNs, but parse_ntfs_boot_sector() decoded them into an s64.\n\nA crafted high-bit value could therefore become negative and pass\nthe existing upper-bound check. The invalid value then propagated into\nthe MFT zone allocator and could result in an out-of-bounds access to\nlcn_empty_bits_per_page.","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":"ntfs: reject invalid MFT LCNs from boot sector","id":"CVE-2026-89612","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"integer_overflow","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"ntfs: reject invalid empty mapping pairs","id":"CVE-2026-89613"},"packages":[],"prev":{"headline":"ntfs: validate non-resident attribute offsets","id":"CVE-2026-89611"},"products":["Linux"],"published":"2026-09-11","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-10-19","vendors":["Linux"]},"summary":"A crafted NTFS image can cause an integer overflow leading to out-of-bounds memory access, potentially crashing the system.","url":"https://insights.sbomify.com/CVE-2026-89612/"}