# CVE-2026-80529: xfs: don't swallow dquot recovery verification errors


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 26 Aug 2026
- **Updated:** 26 Aug 2026
- **Also known as:** AZL-97811, BELL-CVE-2026-80529, DEBIAN-CVE-2026-80529, UBUNTU-CVE-2026-80529

## What is CVE-2026-80529?

CVE-2026-80529 is a vulnerability in Linux, published on 26 Aug 2026. 

### Official description

In the Linux kernel, the following vulnerability has been resolved:

xfs: don't swallow dquot recovery verification errors

xlog_recover_dquot_commit_pass2() validates the recovered dquot with
xfs_dqblk_verify() and, on failure, sets error = -EFSCORRUPTED and jumps
to out_release.  But out_release unconditionally returns 0, so the
corruption error is discarded: the caller xlog_recover_items_pass2()
sees success, log recovery proceeds as if the dquot were valid, and the
corrupt quota buffer can be written back to disk.

## Which versions are affected by CVE-2026-80529?


## How do I fix CVE-2026-80529?

Upgrade to a fixed version.

## Is CVE-2026-80529 being exploited?

There is no known exploitation of CVE-2026-80529 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-80529 and fix it if it is affected.

What it is: CVE-2026-80529 is a vulnerability in Linux, published on 26 Aug 2026. 
Exploitation: There is no known exploitation of CVE-2026-80529 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-80529/ (Markdown: https://insights.sbomify.com/CVE-2026-80529/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-80529
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-80529
- OSV: https://osv.dev/vulnerability/CVE-2026-80529

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-80529/
Summaries are generated and may contain mistakes; the official description above is the record.