f2fs: only redirty pinned folios in redirty_blocks
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
6.18.517.2.57.3In 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.
From the CVE record · Linux
The Linux kernel's f2fs redirty_blocks() can drop one folio reference too many if read_cache_folio() fails before pinning anything and readahead has already populated that folio in the page cache. A later drop_caches or reclaim operation can report “BUG: Bad page state.” The input does not specify an attacker path, authentication requirements, or user interaction.
Engineers running Linux kernels with f2fs should check their kernel; affected versions are not specified.