Vulnerability · CVE-2026-99080
CVE-2026-99080: fs: Free any excess xarray nodes in clear_inode()
Published Oct 23, 2026 · catalog updated Oct 25, 2026 · Linux Linux
Last checked Nov 6, 2026. A connected source was read within the last 7 days.
Check if you run it
No confirmed exploitation is on record for CVE-2026-99080. EPSS is 0.20%. Act only if a listed version of Linux Linux is installed.
Gaps on this record
- No vendor fix or required action is stored. Compare the linked advisory before you change production.
Same product and reporting
- CVE-2026-99260 · Medium
- CVE-2026-99259 · Medium
- CVE-2026-99258 · High
- CVE-2026-99257 · Medium
- CVE-2026-99255 · Medium
- Severity
- High—
- Known exploitation
- Not in CISA/VulnCheck KEV
- EPSS
- 0.20%
- Remediation
- Advisory link
- Affected products
- Linux Kernel · linux kernel · vendor Linux Linux
From: Greg Kroah-Hartman 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. The Linux kernel CVE team has assigned CVE-2026-99080 to this issue. Affected and fixed versions =====
Are you affected?
Enter the version you run. The result uses only the ranges stored on this record.
The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.
- Linux Kernel0 → 6.6.160; 6.7.0 → 6.12.113; 6.13.0 → 6.18.57
- linux kernelversion unspecified
- vendor Linux Linuxversion unspecified
How to fix CVE-2026-99080
Upgrade
CVE-2026-99080 lists a fix boundary at 6.6.160. Compare the installed build with that boundary before you change production.
Version check
Fixed in 6.6.160; 6.7.0
Advisory
Open the cve_org record and follow its fix.
Official advisories
What to do
Three questions, each answered from this record only. Confirm the vendor advisory before you patch.
Should you patch?
No confirmed exploitation is on record for CVE-2026-99080. EPSS is 0.20%. Act only if a listed version of Linux Linux is installed.
Which versions are affected?
Compare what you have installed with Kernel 0 → 6.6.160; 6.7.0 → 6.12.113; 6.13.0 → 6.18.57. Compare the installed version with the linked vendor advisory before you change production.
What should an analyst verify?
No weakness class is stored. EPSS 0.20%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.
Code
The project this record applies to. Exploit listings stay in References.
Timeline
Detection, updates, and resolution for this record.
Oct 23, 2026 · Linux Kernel CVE
Detected
From: Greg Kroah-Hartman 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,
Oct 25, 2026 · OpenSSF OSV / OSV Scanner
Fix available
Kernel fixed in 6.6.160; Kernel fixed in 6.12.113; Kernel fixed in 6.18.57; Kernel fixed in 7.2.11
Oct 25, 2026 · OpenSSF OSV / OSV Scanner
Fix available
Kernel fixed in 6.6.160; 6.7.0
Oct 25, 2026 · OpenSSF OSV / OSV Scanner
Updated
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
Sources
- CVE.orgVulnerability recordCVE-2026-99080
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 i
cve.org - FIRST EPSSExploitation probabilityCVE-2026-99080
30-day exploitation probability 0.20%
first.org - Linux Kernel CVEVendor advisoryCVE-2026-99080
From: Greg Kroah-Hartman 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. Rece
git.kernel.org - OpenSSF OSV / OSV ScannerPackage advisoryCVE-2026-99080
fs: Free any excess xarray nodes in clear_inode()
osv.dev - Tenable CVE DatabaseVulnerability recordCVE-2026-99080
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
tenable.com
References
Freshness
Last verified in this catalog Nov 6, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.
- FIRST EPSSOct 31, 2026
- OpenSSF OSV / OSV ScannerOct 25, 2026
- Tenable CVE DatabaseOct 23, 2026
- CVE.orgOct 23, 2026
- Linux Kernel CVEOct 23, 2026