{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-72364 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-72364 is a high-severity denial of service 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-72364 and fix it if it is affected.\n\nWhat it is: CVE-2026-72364 is a high-severity denial of service 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-72364 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-72364/ (Markdown: https://insights.sbomify.com/CVE-2026-72364/index.md)","id":"CVE-2026-72364","markdown":"https://insights.sbomify.com/CVE-2026-72364/index.md","name":"CVE-2026-72364","record":{"aliases":["BELL-CVE-2026-72364","DEBIAN-CVE-2026-72364","GHSA-98p8-g3h5-vfv6","UBUNTU-CVE-2026-72364"],"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 flaw in Linux kernel netfs writeback error handling can lead to denial of service due to improper state cleanup and folio locking.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H","version":"3.1"},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nnetfs: Fix writeback error handling\n\nFix the error handling in writeback_iter() loop.  If an error occurs,\nwriteback_iter() needs to be called again with *error set to the error so\nthat it can clean up iteration state.  Further, the current folio needs\nunlocking and redirtying.","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":"netfs: Fix writeback error handling","id":"CVE-2026-72364","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"netfs: Fix writethrough to use collection offload","id":"CVE-2026-72365"},"packages":[],"prev":{"headline":"netfs: Fix folio state after ENOMEM whilst under writeback iteration","id":"CVE-2026-72363"},"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-17","vendors":["Linux"]},"summary":"A flaw in Linux kernel netfs writeback error handling can lead to denial of service due to improper state cleanup and folio locking.","url":"https://insights.sbomify.com/CVE-2026-72364/"}