Live › vulnerability › CVE-2026-99080
Go to dashboardThe Linux kernel's inode clearing path leaked xarray tree nodes in rare cases, and recent reports show that madvise calls can trigger the leak on demand. The fix frees any leftover nodes when an inode is cleared, which stops the memory from accumulating.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
No product ranges from the sources yet.
Unknown from the sources.
Unknown from the sources.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2026-99080")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.