CVE-2026-99080: Linux kernel · fs: Free any excess xarray nodes in clear_inode()
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in f1c966eb6ed5e190c90a56c5bdaa69967de39f21 : update Linux kernel when convenient.
Data as of 26 Oct 2026, 12:55 UTC
Rated Low by Threat Radar's AI analysis · CVSS not yet scored by NVD
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 4% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in f1c966eb6ed5e190c90a56c5bdaa69967de39f21, ee3f011250104129893d8e9599147e457d4d7280, 50cff3f112d64db6e5f57355f79bc837db8fe132 +2
Exploitation evidence
Disclosed: evidence found.
CVE published 23 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
AI-suggested
The vulnerability has been fixed in the Linux kernel by applying patches that call xa_destroy() in clear_inode(). Users should update to a fixed kernel version containing the referenced commits to remediate this issue.
Description
A memory leak vulnerability in the Linux kernel's clear_inode() function related to xarray nodes has been resolved. The issue involved a hard-to-hit leak of xarray nodes that could be triggered by certain operations such as madvise. The fix involves calling xa_destroy() to free excess xarray nodes and cycle the i_pages lock, addressing the leak more effectively.
References
- git.kernel.org/stable/c/f1c966eb6ed5e190c90a56c5bdaa69967de39f21 (opens in a new tab)
- git.kernel.org/stable/c/21f51434c47d8628b62275ae6c6ad6b573abcd02 (opens in a new tab)
- git.kernel.org/stable/c/50cff3f112d64db6e5f57355f79bc837db8fe132 (opens in a new tab)
- git.kernel.org/stable/c/43f830e2bb84b22ca824b20bb861d823ecb520bd (opens in a new tab)
- git.kernel.org/stable/c/ee3f011250104129893d8e9599147e457d4d7280 (opens in a new tab)