{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-72199 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-72199 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-72199 and fix it if it is affected.\n\nWhat it is: CVE-2026-72199 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-72199 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-72199/ (Markdown: https://insights.sbomify.com/CVE-2026-72199/index.md)","id":"CVE-2026-72199","markdown":"https://insights.sbomify.com/CVE-2026-72199/index.md","name":"CVE-2026-72199","record":{"aliases":["DEBIAN-CVE-2026-72199","GHSA-r953-ww6g-j7cw","UBUNTU-CVE-2026-72199"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Linux kernel NTFS driver","requires_auth":"none","summary":"Missing validation of NTFS index root headers can cause kernel crashes, requiring a patch to enforce alignment and size invariants.","user_interaction":"not_required","vuln_class":"null_dereference"},"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: validate resident index root values on lookup\n\nResident $INDEX_ROOT values carry index header fields that callers\nconsume after lookup. Some callers already validate parts of the layout\nbefore walking entries, but those checks are scattered and do not cover\nall root header invariants, such as entries_offset alignment and lower\nbound, index_length, and allocated_size consistency.\n\nThe resident root resize paths now keep these header fields consistent\nwhile the value size changes: ntfs_ir_truncate() lowers\nindex.allocated_size before shrinking the resident value, and\nntfs_ir_reparent() grows the resident value before publishing a larger\nroot header. Lookup-time validation can therefore cover these invariants\nwithout tripping over the driver's own resize paths.\n\nAdd $INDEX_ROOT to the minimum resident value size table and validate the\nresident index header fields before returning the attribute from lookup.\nRequire 8-byte aligned index header fields, a sane entries_offset, an\nindex_length within allocated_size, allocated_size within the resident\nvalue, and enough entry space for at least an index entry header.\n\nThe shared validator already rejects non-resident records for\nresident-only attribute types, including $INDEX_ROOT.","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: validate resident index root values on lookup","id":"CVE-2026-72199","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"ntfs: detect mapping-pairs LCN accumulator overflow","id":"CVE-2026-72200"},"packages":[],"prev":{"headline":"ntfs: reject non-resident records for resident-only attributes","id":"CVE-2026-72198"},"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-18","vendors":["Linux"]},"summary":"Missing validation of NTFS index root headers can cause kernel crashes, requiring a patch to enforce alignment and size invariants.","url":"https://insights.sbomify.com/CVE-2026-72199/"}