# CVE-2026-80805: xfs: validate attr entry pointer before field access

> An out-of-bounds read in the XFS filesystem allows attackers to cause a denial of service or read sensitive memory.

- **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:** 4 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-99516, BELL-CVE-2026-80805, DEBIAN-CVE-2026-80805, GHSA-m3h7-xg69-2hcv, UBUNTU-CVE-2026-80805

## What is CVE-2026-80805?

CVE-2026-80805 is a memory corruption vulnerability in Linux, published on 4 Sep 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: validate attr entry pointer before field access

xfs_attr3_leaf_verify_entry() accesses lentry/rentry fields (namelen,
valuelen) before checking if the entry pointer itself is within bounds.
If nameidx is crafted to point near the end of the buffer, these field
accesses can read out-of-bounds before the bounds check at
name_end > buf_end is performed.

Add explicit bounds checks for entry pointers before accessing their
fields. Use offsetof() to check that the start of the flexible array
member (nameval/name) is within bounds, which ensures all preceding
fields are safe to access.

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


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

Apply the vendor's patch.

## Is CVE-2026-80805 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-80805 is a memory corruption vulnerability in Linux, published on 4 Sep 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-80805 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-80805/ (Markdown: https://insights.sbomify.com/CVE-2026-80805/index.md)
```

## Sources

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

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