fs: Free any excess xarray nodes in clear_inode()
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.6.160, 6.12.113, 6.18.57, 7.2.11
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
Timeline
- CVE published
- First seen by cve.now
- Record last updated
Affected versions
- Linux Linux
From 77da9389b9d5f07d54fda092d1ab56002ec0019a · fixed in f1c966eb6ed5e190c90a56c5bdaa69967de39f21; From 77da9389b9d5f07d54fda092d1ab56002ec0019a · fixed in 21f51434c47d8628b62275ae6c6ad6b573abcd02; From 77da9389b9d5f07d54fda092d1ab56002ec0019a · fixed in 50cff3f112d64db6e5f57355f79bc837db8fe132; From 77da9389b9d5f07d54fda092d1ab56002ec0019a · fixed in 43f830e2bb84b22ca824b20bb861d823ecb520bd; From 77da9389b9d5f07d54fda092d1ab56002ec0019a · fixed in ee3f011250104129893d8e9599147e457d4d7280
- Linux Linux
4.20
- KernelLinux
fixed in 6.6.160; From 6.7.0 · fixed in 6.12.113; From 6.13.0 · fixed in 6.18.57; From 6.19.0 · fixed in 7.2.11