# CVE-2026-80538: xfs: propagate errors from xfs_rtginode_load


- **Severity:** High 7.1 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 26 Aug 2026
- **Updated:** 27 Aug 2026
- **Also known as:** BELL-CVE-2026-80538, DEBIAN-CVE-2026-80538, GHSA-5q37-jjr8-c4m5, UBUNTU-CVE-2026-80538

## What is CVE-2026-80538?

CVE-2026-80538 is a high-severity vulnerability in Linux, published on 26 Aug 2026. 

### Official description

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

xfs: propagate errors from xfs_rtginode_load

xfs_rtginode_ensure() treats every xfs_rtginode_load() error other than
-ENOENT as success.  This can leave the realtime group inode unset after an
I/O, allocation, or corruption error.  Growfs then continues as though the
inode had been loaded.

Only -ENOENT means that the inode needs to be created.  Return all other
errors to the growfs caller.

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


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

Upgrade to a fixed version.

## Is CVE-2026-80538 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-80538 is a high-severity vulnerability in Linux, published on 26 Aug 2026. 
Exploitation: There is no known exploitation of CVE-2026-80538 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-80538/ (Markdown: https://insights.sbomify.com/CVE-2026-80538/index.md)
```

## Sources

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

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