f2fs: fix to migrate all curseg types during free_segment_range
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ d0b9e42ab6155dc05fc83f00af9f45d4dd02264d · < 8ec06f50ddd8d201bd7e55b896ae28ed9d4cb7d1| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
f2fs: fix to migrate all curseg types during free_segment_range
In free_segment_range(), the curseg evacuation loop only iterates up to NR_CURSEG_PERSIST_TYPE (0..5), missing non-persistent in-memory curseg types such as CURSEG_COLD_DATA_PINNED and CURSEG_ALL_DATA_ATGC.
Even though these in-memory curseg types are not saved in the on-disk checkpoint header, they still occupy active physical segments at runtime. If an active in-memory curseg happens to be allocated within the segment range being truncated during filesystem shrink, failing to evacuate it will cause subsequent writes to the curseg attempting out-of-bounds I/O on the truncated storage range.
Fix this by expanding the curseg evacuation loop upper bound to NR_CURSEG_TYPE to ensure all active curseg types are safely migrated out of the target range.
From the CVE record · Linux
The Linux kernel’s f2fs filesystem shrink operation may fail to move certain active in-memory segments out of the range being truncated. If one of those segments is in that range, subsequent writes can attempt out-of-bounds I/O. The input does not specify an attacker access requirement or user-interaction condition.
Engineers running Linux systems that use f2fs should check their kernel versions; affected versions are not specified.