{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-72205 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-72205 is a 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-72205 and fix it if it is affected.\n\nWhat it is: CVE-2026-72205 is a 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-72205 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-72205/ (Markdown: https://insights.sbomify.com/CVE-2026-72205/index.md)","id":"CVE-2026-72205","markdown":"https://insights.sbomify.com/CVE-2026-72205/index.md","name":"CVE-2026-72205","record":{"aliases":["DEBIAN-CVE-2026-72205","GHSA-cx24-8ppf-cvpr","UBUNTU-CVE-2026-72205"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"low_privilege","summary":"A memory leak in the Linux kernel NTFS driver allows local attackers to exhaust system memory by repeatedly triggering mount failures, leading to denial of service.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nntfs: free volume-wide resources on fill_super failure\n\nntfs_fill_super()'s err_out_now path frees only the volume struct via\nkfree(vol), leaving several vol-owned allocations behind on every mount\nfailure:\n\n  - vol-\u003enls_map, loaded by ntfs_init_fs_context() via\n    load_nls_default() (or replaced by an explicit nls= option in\n    ntfs_parse_param()), is never unload_nls()'d.\n\n  - vol-\u003evolume_label, allocated by load_system_files() through\n    ntfs_ucstonls() once the $Volume name attribute has been parsed, is\n    not released by load_system_files()'s own error labels nor by the\n    fill_super() inline cleanup that only runs on d_make_root()\n    failure.  Any later failure inside load_system_files() leaks it.\n\n  - vol-\u003elcn_empty_bits_per_page was kvfree()'d in\n    unl_upcase_iput_tmp_ino_err_out_now without clearing the pointer,\n    so it could not be folded into a single common cleanup.\n\nBecause the failure paths never call ntfs_volume_free() and never reach\nthe d_make_root() inline cleanup block (it sits above the label and is\njumped over by the load_system_files() / kvmalloc failure gotos), these\nresources accumulate per failed mount attempt with no chance of\nrecovery short of unloading the module.  This is a silent leak: the\ninodes loaded prior to failure remain hashed but generic_shutdown_super()\nskips evict_inodes() when sb-\u003es_root is unset, so no CHECK_DATA_CORRUPTION\nwarning is emitted either.\n\nMove the per-volume frees down to err_out_now and drop the\nlcn_empty_bits_per_page kvfree() from the upper label so the cleanup is\nperformed exactly once on every failure path.  Using unconditional\nkvfree() / kfree() / unload_nls() is safe because they all accept NULL\nand the upper labels that previously freed nls_map (the d_make_root()\ninline cleanup) already clear the pointer.","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: free volume-wide resources on fill_super failure","id":"CVE-2026-72205","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"ntfs: validate index block header more strictly","id":"CVE-2026-72206"},"packages":[],"prev":{"headline":"ntfs: centalize $INDEX_ROOT header validation","id":"CVE-2026-72204"},"products":["Linux"],"published":"2026-08-15","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-08-18","vendors":["Linux"]},"summary":"A memory leak in the Linux kernel NTFS driver allows local attackers to exhaust system memory by repeatedly triggering mount failures, leading to denial of service.","url":"https://insights.sbomify.com/CVE-2026-72205/"}