CVE Catalog

CVE-2026-99080

Unknown
Published: Translated: NVD NIST

Summary

In the Linux kernel, clear_inode() has an xarray node leak that can be triggered, among other ways, via madvise. Rather than fixing the leaks where they occur, the fix calls xa_destroy(), which has the side effect of cycling the i_pages lock.

Risk Assessment

A kernel memory leak can lead to gradual resource exhaustion and eventually denial of service. It requires local invocation of specific filesystem operations.

Recommendation

Update the Linux kernel to a version containing the fix. Monitor kernel memory usage on systems exposed to madvise calls.

Other vulnerabilities in Linux kernel

See all
Original NVD description (English source)

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.

Vulnerability data from NVD (NIST) · CISA KEV · EPSS