# CVE-2026-80532: xfs: fix another iunlink infinite loop bug in online fsck

> An infinite loop in the XFS online fsck component allows local attackers to cause a denial of service by triggering specific unlinked list conditions.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 26 Aug 2026
- **Updated:** 26 Aug 2026
- **Also known as:** BELL-CVE-2026-80532, DEBIAN-CVE-2026-80532, UBUNTU-CVE-2026-80532

## What is CVE-2026-80532?

CVE-2026-80532 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 another iunlink infinite loop bug in online fsck

xrep_iunlink_resolve_bucket is supposed to reconstruct as much of the
incore prev and next unlinked list pointers based on what it finds on
disk and in memory before we move on to relinking the truly lost inodes
back into the unlinked list.  However, it's still vulnerable to infinite
loops that come in via the next_unlinked pointers.

Fix this problem by remembering which inodes we've already seen and
checking new agino pointers against that.  If a bit is already set,
either this is a loop or the inode has nonzero link count.  We'll deal
with the second case in a subsequent patch.

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


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

Apply the vendor's patch.

## Is CVE-2026-80532 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-80532 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-80532 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-80532/ (Markdown: https://insights.sbomify.com/CVE-2026-80532/index.md)
```

## Sources

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

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