{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-80529 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2026-80529 is a vulnerability in Linux, published on 26 Aug 2026."},"fix_prompt":"Check this codebase for CVE-2026-80529 and fix it if it is affected.\n\nWhat it is: CVE-2026-80529 is a vulnerability in Linux, published on 26 Aug 2026. \nExploitation: There is no known exploitation of CVE-2026-80529 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-80529/ (Markdown: https://insights.sbomify.com/CVE-2026-80529/index.md)","id":"CVE-2026-80529","markdown":"https://insights.sbomify.com/CVE-2026-80529/index.md","name":"CVE-2026-80529","record":{"aliases":["AZL-97811","BELL-CVE-2026-80529","DEBIAN-CVE-2026-80529","UBUNTU-CVE-2026-80529"],"analysis":null,"analysis_generated_by":null,"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\nxfs: don't swallow dquot recovery verification errors\n\nxlog_recover_dquot_commit_pass2() validates the recovered dquot with\nxfs_dqblk_verify() and, on failure, sets error = -EFSCORRUPTED and jumps\nto out_release.  But out_release unconditionally returns 0, so the\ncorruption error is discarded: the caller xlog_recover_items_pass2()\nsees success, log recovery proceeds as if the dquot were valid, and the\ncorrupt quota buffer can be written back to disk.","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":"xfs: don't swallow dquot recovery verification errors","id":"CVE-2026-80529","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":6,"next":{"headline":"xfs: fix exchange-range reflink flag clearing issue with INO1_WRITTEN","id":"CVE-2026-80530"},"packages":[],"prev":{"headline":"ceph: avoid fs reclaim while using current-\u003ejournal_info","id":"CVE-2026-80528"},"products":["Linux"],"published":"2026-08-26","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-26","vendors":["Linux"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-80529/"}