{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-72196 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-72196 is a high-severity memory corruption 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-72196 and fix it if it is affected.\n\nWhat it is: CVE-2026-72196 is a high-severity memory corruption 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-72196 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-72196/ (Markdown: https://insights.sbomify.com/CVE-2026-72196/index.md)","id":"CVE-2026-72196","markdown":"https://insights.sbomify.com/CVE-2026-72196/index.md","name":"CVE-2026-72196","record":{"aliases":["BELL-CVE-2026-72196","DEBIAN-CVE-2026-72196","GHSA-7v7p-59m6-6h9x","UBUNTU-CVE-2026-72196"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["code_execution","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 out-of-bounds writes during log replay, potentially leading to memory corruption or system crashes.","user_interaction":"not_required","vuln_class":"memory_corruption"},"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 copy_lcns dp-\u003epage_lcns[] index in analysis pass\n\nIn log_replay()'s analysis pass, after find_dp() returns a\nvalid DIR_PAGE_ENTRY for the (target_attr, target_vcn) tuple,\nthe copy_lcns block walks lrh-\u003elcns_follow further entries:\n\n\tt16 = le16_to_cpu(lrh-\u003elcns_follow);\n\tfor (i = 0; i \u003c t16; i++) {\n\t    size_t j = (size_t)(le64_to_cpu(lrh-\u003etarget_vcn) -\n\t                        le64_to_cpu(dp-\u003evcn));\n\t    dp-\u003epage_lcns[j + i] = lrh-\u003epage_lcns[i];\n\t}\n\nfind_dp() only validates that target_vcn falls within\n[dp-\u003evcn, dp-\u003evcn + dp-\u003elcns_follow), i.e., that the FIRST\ncluster is covered.  The walk through the further entries is\nnot bounded against dp-\u003elcns_follow.  For a malformed LRH\nwhere target_vcn = dp-\u003evcn + dp-\u003elcns_follow - 1 and\nlrh-\u003elcns_follow \u003e 1, the i \u003e 0 writes overflow the dp's\nallocated page_lcns[] array.\n\nAdd the missing j + lrh-\u003elcns_follow \u003c= dp-\u003elcns_follow guard.\n\nReproduced under UML+KASAN on mainline 8d90b09e6741 as a\nslab-out-of-bounds write of size 8 from log_replay+0x68d4 on\nthe mount path.\n\nThis is distinct from Pavitra Jha's 2026-05-02 patch\n(\"fs/ntfs3: validate lcns_follow in log_replay conversion\",\n\u003c20260502154252.164586-1-jhapavitra98@gmail.com\u003e) which\naddresses the separate version-0 dirty-page-table conversion\npath's memmove(\u0026dp-\u003evcn, ...) call.  The two fixes are\ncomplementary; both should land.\n\n[almaz.alexandrovich@paragon-software.com: clang-formatted the changes,\nfixed conflicts]","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 copy_lcns dp-\u003epage_lcns[] index in analysis pass","id":"CVE-2026-72196","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":6,"next":{"headline":"fs/ntfs3: bound DeleteIndexEntryAllocation memmove length","id":"CVE-2026-72197"},"packages":[],"prev":{"headline":"fs/ntfs3: bound attr_off in UpdateResidentValue against data_off","id":"CVE-2026-72195"},"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 out-of-bounds writes during log replay, potentially leading to memory corruption or system crashes.","url":"https://insights.sbomify.com/CVE-2026-72196/"}