# CVE-2026-99080: fs: Free any excess xarray nodes in clear_inode()


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 23 Oct 2026
- **Updated:** 26 Oct 2026
- **Also known as:** AZL-110981, BELL-CVE-2026-99080, DEBIAN-CVE-2026-99080, GHSA-g6p5-3jcv-j9vr, UBUNTU-CVE-2026-99080

## What is CVE-2026-99080?

CVE-2026-99080 is a vulnerability in Linux, published on 23 Oct 2026. 

### Official description

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

fs: Free any excess xarray nodes in clear_inode()

For many years we've had a hard to hit leak of xarray nodes.  Hugh
documented it well in commit 786b31121a2c.  Recently people and
syzbot have found ways to force it to happen with madvise.  Rather
than fix the leaks where they happen, just call xa_destroy() which
has the side-effect of cycling the i_pages lock.

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


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

Upgrade to a fixed version.

## Is CVE-2026-99080 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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