# CVE-2026-80533: xfs: don't walk off the end of a null sc->sa.agi_bp in AGI repair

> A null pointer dereference in the Linux kernel XFS AGI repair code can cause a system crash, requiring local administrative access to trigger.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **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-80533, DEBIAN-CVE-2026-80533, UBUNTU-CVE-2026-80533

## What is CVE-2026-80533?

CVE-2026-80533 is a 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: don't walk off the end of a null sc->sa.agi_bp in AGI repair

LOLLM noticed a longstanding bug where xrep_iunlink_walk_ondisk_bucket
tries to walk ragi->sc->sa.agi_bp to rebuild the unlinked inode lists.
Unfortunately, it's possible for agi_bp to be null if the buffer
verifier fails, so we have to use ragi->agi_bp (which skips verifier
checks) instead.

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


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

Apply the vendor's patch.

## Is CVE-2026-80533 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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