xfs: don't let hidden_space go negative in xfs_metafile_resv_init
- 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.18.55, 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 hidden_space go negative in xfs_metafile_resv_init LOLLM points out that if the amount of fdblocks that we can reserve for a metadata btree file goes below the space already used by that file, then the hidden_space subtraction can underflow, causing xfs_dec_fdblocks to subtract a huge amount of space. We never want the target to be less than the used sapce, so fix the logic that adjusts dblocks_avail downwards. Also fix an error in the adjacent comment.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 1df8d75030b787a9fae270b59b93eef809dd2011 · fixed in 930a9c1c321efdaa3e7f8caecb0479cee3baf342; From 1df8d75030b787a9fae270b59b93eef809dd2011 · fixed in f0d8352a39f4a2e329ae45b71bb0d49e2ca0a6dc; From 1df8d75030b787a9fae270b59b93eef809dd2011 · fixed in 476582d754cdc5110f806001417fea6c77824c13
- Linux Linux
6.15
- KernelLinux
From 6.15.0 · fixed in 6.18.55; From 6.19.0 · fixed in 7.2.9