f2fs: only redirty pinned folios in redirty_blocks
- 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.51, 7.2.5
- 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: f2fs: only redirty pinned folios in redirty_blocks redirty_blocks() pins folios with read_cache_folio() and then walks the same range again with filemap_lock_folio() to redirty them and drop the references it took. Commit 5951fee46bef ("f2fs: Use a folio in redirty_blocks()") changed the second pass to a do/while loop. If read_cache_folio() fails before anything is pinned, page_idx does not advance but the cleanup loop still runs once. If readahead has already populated the failed folio in page cache, that extra iteration finds it and folio_put_refs(folio, 2) drops one reference too many. Later drop_caches or reclaim can then report "BUG: Bad page state". Only redirty the range that was pinned successfully.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 5951fee46befbf6176c86482432f4f76e522f16c · fixed in 445e4a1e6025ecd5312e9a95c1b234192c976ca1; From 5951fee46befbf6176c86482432f4f76e522f16c · fixed in 89c65ec3c18903de763cf567c96ab3ef60e5f3b0; From 5951fee46befbf6176c86482432f4f76e522f16c · fixed in 85171332742e741ccd6f401c69b6e0d698119e72
- Linux Linux
6.16
- KernelLinux
From 6.16.0 · fixed in 6.18.51; From 6.19.0 · fixed in 7.2.5