{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-72195 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-72195 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-72195 and fix it if it is affected.\n\nWhat it is: CVE-2026-72195 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-72195 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-72195/ (Markdown: https://insights.sbomify.com/CVE-2026-72195/index.md)","id":"CVE-2026-72195","markdown":"https://insights.sbomify.com/CVE-2026-72195/index.md","name":"CVE-2026-72195","record":{"aliases":["BELL-CVE-2026-72195","DEBIAN-CVE-2026-72195","GHSA-44j2-h353-38w7","UBUNTU-CVE-2026-72195"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service","data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel NTFS3","requires_auth":"low_privilege","summary":"An integer underflow in the Linux kernel NTFS3 driver allows out-of-bounds reads, potentially causing system crashes or leaking memory contents.","user_interaction":"not_required","vuln_class":"integer_overflow"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":7.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/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\nfs/ntfs3: bound attr_off in UpdateResidentValue against data_off\n\nIn do_action()'s UpdateResidentValue case (fslog.c:3307),\nlrh-\u003eattr_off and lrh-\u003eredo_len come from the on-disk LRH.\nWhen they satisfy aoff + dlen \u003c attr-\u003eres.data_off, the\nassignment\n\n\tattr-\u003eres.data_size = cpu_to_le32(aoff + dlen - data_off);\n\nunderflows to ~4 GiB (e.g. 0xFFFFFFF9 when aoff=0x10, dlen=1,\ndata_off=0x18).  Subsequent code that reads attr-\u003eres.data_size\nto walk the resident attribute payload would then read up to\n4 GiB past the 1024-byte MFT record allocation.\n\nThe existing mi_enum_attr() defense in fs/ntfs3/record.c:287\ncatches the corrupted data_size on the next attribute walk\nand fails the mount, but only on the path that walks all\nattributes.  A read site that picks an attribute by name and\nreads its data_size without re-validating is not covered.\nValidate aoff against data_off and asize at the source.\n\nReproduced under UML+KASAN on mainline 8d90b09e6741 via\npr_warn-only probe: with aoff=0x10 and data_off=0x18, the\npost-assignment data_size is 0xfffffff9 (mount then fails\nat -22 from mi_enum_attr).\n\n[almaz.alexandrovich@paragon-software.com: clang-formatted the changes]","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":"fs/ntfs3: bound attr_off in UpdateResidentValue against data_off","id":"CVE-2026-72195","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"integer_overflow","year":"2026"},"n_packages":0,"n_references":7,"next":{"headline":"fs/ntfs3: bound copy_lcns dp-\u003epage_lcns[] index in analysis pass","id":"CVE-2026-72196"},"packages":[],"prev":{"headline":"fs/ntfs3: add depth limit to indx_find_buffer to prevent stack overflow","id":"CVE-2026-72194"},"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":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-10-16","vendors":["Linux"]},"summary":"An integer underflow in the Linux kernel NTFS3 driver allows out-of-bounds reads, potentially causing system crashes or leaking memory contents.","url":"https://insights.sbomify.com/CVE-2026-72195/"}