Linux kernel memory leak in clear_inode() xarray cleanup
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 77da9389b9d5f07d54fda092d1ab56002ec0019a · < 50cff3f112d64db6e5f57355f79bc837db8fe132| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel can leak xarray nodes associated with an inode. The leak is hard to trigger, but madvise can be used to force it; the input does not specify network access, authentication, or user-interaction requirements.
Teams running Linux kernels should check their versions against the vendor advisory; affected versions are not specified.