All reports
Low

kernel: fs: Free any excess xarray nodes in clear_inode()

Affected versions

Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported

Exploitation

CVE-2026-99080

Probability of exploitation in the next 30 days: 0.20%

FIRST EPSS · 2026-11-20

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.

A flaw was found in the Linux kernel's file system component. When freeing file index records (inodes), the kernel could fail to release unused internal data tracking nodes (xarray nodes) left behind during memory management operations. A local user could exploit this flaw to cause a persistent kernel memory leak, ultimately leading to a Denial of Service (DoS) through system memory exhaustion.