{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-72197 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-72197 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-72197 and fix it if it is affected.\n\nWhat it is: CVE-2026-72197 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-72197 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-72197/ (Markdown: https://insights.sbomify.com/CVE-2026-72197/index.md)","id":"CVE-2026-72197","markdown":"https://insights.sbomify.com/CVE-2026-72197/index.md","name":"CVE-2026-72197","record":{"aliases":["BELL-CVE-2026-72197","DEBIAN-CVE-2026-72197","GHSA-j9fv-qm2v-gr26","UBUNTU-CVE-2026-72197"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel NTFS3","requires_auth":"none","summary":"A missing bounds check in the Linux kernel NTFS3 driver allows a crafted image to cause a kernel oops via an integer overflow in memmove.","user_interaction":"not_required","vuln_class":"integer_overflow"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":8.4,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/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\nfs/ntfs3: bound DeleteIndexEntryAllocation memmove length\n\nIn do_action()'s DeleteIndexEntryAllocation case, e-\u003esize comes\nfrom an on-disk INDEX_BUFFER entry.  When e-\u003esize makes\ne + e-\u003esize point past hdr + hdr-\u003eused,\nPtrOffset(e1, Add2Ptr(hdr, used)) returns a negative ptrdiff_t\nthat is silently cast to a quasi-infinite size_t when passed\nto memmove().  The memmove then walks past the destination\nbuffer.\n\nThe sibling DeleteIndexEntryRoot case at fslog.c:3540-3543\nalready carries the corresponding guard:\n\n\tif (PtrOffset(e1, Add2Ptr(hdr, used)) \u003c esize ||\n\t    Add2Ptr(e, esize) \u003e Add2Ptr(lrh, rec_len) ||\n\t    used + esize \u003e le32_to_cpu(hdr-\u003etotal)) {\n\t\tgoto dirty_vol;\n\t}\n\nApply the same shape to the allocation-path case.  Also reject\nesize == 0: memmove(e, e, ...) is a no-op and leaves\nhdr-\u003eused unchanged, hiding a malformed entry from the\nexisting check_index_header() walk.\n\nReproduced under UML+KASAN on mainline 8d90b09e6741 by\nmounting a crafted NTFS image: the unguarded memmove takes a\nlength of 0xffffffffffffff00 and the kernel oopses in\nmemmove+0x81/0x1a0 on the do_action+0x36a2 frame.\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 DeleteIndexEntryAllocation memmove length","id":"CVE-2026-72197","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":"ntfs: reject non-resident records for resident-only attributes","id":"CVE-2026-72198"},"packages":[],"prev":{"headline":"fs/ntfs3: bound copy_lcns dp-\u003epage_lcns[] index in analysis pass","id":"CVE-2026-72196"},"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":"A missing bounds check in the Linux kernel NTFS3 driver allows a crafted image to cause a kernel oops via an integer overflow in memmove.","url":"https://insights.sbomify.com/CVE-2026-72197/"}