# CVE-2026-80534: xfs: fix ilock leak on error in xfs_dq_get_next_id

> A local attacker can trigger a lock leak in the XFS quota subsystem, causing subsequent quota operations to hang and resulting in a denial of service.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 26 Aug 2026
- **Updated:** 27 Aug 2026
- **Also known as:** AZL-97683, BELL-CVE-2026-80534, DEBIAN-CVE-2026-80534, GHSA-cm36-67fx-7wvw, UBUNTU-CVE-2026-80534

## What is CVE-2026-80534?

CVE-2026-80534 is a denial of service vulnerability in Linux, published on 26 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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

xfs: fix ilock leak on error in xfs_dq_get_next_id

xfs_dq_get_next_id() takes the quota inode ILOCK before calling
xfs_iread_extents().  If xfs_iread_extents() fails, the function returns
immediately without releasing the lock, leaking the quota inode ILOCK.
This can leave the quota inode locked and cause subsequent quota
operations to hang.

Fix this by jumping to a common unlock path on error instead of returning
directly.

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


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

Apply the vendor's patch.

## Is CVE-2026-80534 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-80534 is a denial of service vulnerability in Linux, published on 26 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-80534 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-80534/ (Markdown: https://insights.sbomify.com/CVE-2026-80534/index.md)
```

## Sources

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

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