xfs: don't let memory failures leak blocks and kill repairs
- 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.12.113, 6.18.56, 7.2.9
- 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: xfs: don't let memory failures leak blocks and kill repairs LOLLM complains that a memory allocation failure in xrep_newbt_add_blocks results in online repair leaking blocks that were previously allocated to write a new btree, but the problem is worse than that -- a limitation of the codebase is that the callers cannot undo the transaction /and/ return the error -- either you undo all changes and commit the transaction, or you error out and the filesystem goes down. However, the new btree space reservation object isn't that big (~48 bytes). Let's just do a NOFAIL allocation and the problem goes away.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From be408417630427984a1fddd069f30b245793234c · fixed in 3380151cf0ce8ad0c1d356fed51e4b69e1d28e50; From be408417630427984a1fddd069f30b245793234c · fixed in b15c79fca28060fd9c7e77f2c3ebc4ba023974e8; From be408417630427984a1fddd069f30b245793234c · fixed in 0e0d3372a84029da1768c7a4c4601484af5b58a2; From be408417630427984a1fddd069f30b245793234c · fixed in ab1c416d2377cdc16123ef521aac4da1c468c3d4
- Linux Linux
6.8
- KernelLinux
From 6.8.0 · fixed in 6.12.113; From 6.13.0 · fixed in 6.18.56; From 6.19.0 · fixed in 7.2.9