CVE-2026-99080: fs: Free any excess xarray nodes in clear_inode()

CVE-2026-99080: fs: Free any excess xarray nodes in clear_inode()

[Greg Kroah-Hartman]

From: Greg Kroah-Hartman <gregkh@kernel.org>

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.

The Linux kernel CVE team has assigned CVE-2026-99080 to this issue.


Affected and fixed versions
===========================

	Fixed in 6.6.160 with commit f1c966eb6ed5e190c90a56c5bdaa69967de39f21
	Fixed in 6.12.113 with commit 21f51434c47d8628b62275ae6c6ad6b573abcd02
	Fixed in 6.18.57 with commit 50cff3f112d64db6e5f57355f79bc837db8fe132
	Fixed in 7.2.11 with commit 43f830e2bb84b22ca824b20bb861d823ecb520bd
	Fixed in 7.3 with commit ee3f011250104129893d8e9599147e457d4d7280

Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.

Unaffected versions might change over time as fixes are backported to
older supported kernel versions.  The official CVE entry at
	https://cve.org/CVERecord/?id=CVE-2026-99080
will be updated if fixes are backported, please check that for the most
up to date information about this issue.


Affected files
==============

The file(s) affected by this issue are:
	fs/inode.c


Mitigation
==========

The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes.  Individual
changes are never tested alone, but rather are part of a larger kernel
release.  Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all.  If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
	https://git.kernel.org/stable/c/f1c966eb6ed5e190c90a56c5bdaa69967de39f21
	https://git.kernel.org/stable/c/21f51434c47d8628b62275ae6c6ad6b573abcd02
	https://git.kernel.org/stable/c/50cff3f112d64db6e5f57355f79bc837db8fe132
	https://git.kernel.org/stable/c/43f830e2bb84b22ca824b20bb861d823ecb520bd
	https://git.kernel.org/stable/c/ee3f011250104129893d8e9599147e457d4d7280