Answer in brief
CVE-2026-99080 records a Unknown severity vulnerability in fs: Free any excess xarray nodes in clear_inode(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <f1c966eb6ed5e190c90a56c5bdaa69967de39f21 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <21f51434c47d8628b62275ae6c6ad6b573abcd02 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <50cff3f112d64db6e5f57355f79bc837db8fe132 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <43f830e2bb84b22ca824b20bb861d823ecb520bd || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <ee3f011250104129893d8e9599147e457d4d7280 || >=0 <6.6.160 || >=0 <6.12.113 || >=0 <6.18.57 || >=0 <7.2.11 | f1c966eb6ed5e190c90a56c5bdaa69967de39f21, 21f51434c47d8628b62275ae6c6ad6b573abcd02, 50cff3f112d64db6e5f57355f79bc837db8fe132, 43f830e2bb84b22ca824b20bb861d823ecb520bd, ee3f011250104129893d8e9599147e457d4d7280, 6.6.160, 6.12.113, 6.18.57, 7.2.11 |
Published upstream
Oct 23, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 23, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 23, 2026
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.
Quoted source text, attributed separately from HOL analysis.