CVE-2026-99080

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.

Is your site exposed to CVE-2026-99080?

Run a free security scan — no signup, results in seconds.

EPSS — Exploit Prediction

0.0020

Probability of exploitation

0.10%

Percentile rank

EPSS estimates the probability that this vulnerability will be exploited in the wild within the next 30 days. A higher score means more likely to be exploited.

References

Other References

https://git.kernel.org/stable/c/21f51434c47d8628b62275ae6c6ad6b573abcd02 https://git.kernel.org/stable/c/43f830e2bb84b22ca824b20bb861d823ecb520bd https://git.kernel.org/stable/c/50cff3f112d64db6e5f57355f79bc837db8fe132 https://git.kernel.org/stable/c/ee3f011250104129893d8e9599147e457d4d7280 https://git.kernel.org/stable/c/f1c966eb6ed5e190c90a56c5bdaa69967de39f21

Frequently Asked Questions

What is CVE-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 of cycling the i_pages lock.

How do I check if I'm vulnerable to CVE-2026-99080? +

You can use Secably's free Website Scanner to check your website for known vulnerabilities. For infrastructure scanning, use the Port Scanner to identify exposed services that may be affected. Check the vendor advisories linked above for specific patch and version information.