f2fs: fix missing read bio submission on large folio error
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 |
|
|
In the Linux kernel, the following vulnerability has been resolved:
f2fs: fix missing read bio submission on large folio error
f2fs_read_data_large_folio() can keep a read bio across multiple readahead folios. If a later folio hits an error before any of its blocks are added to the bio, folio_in_bio is false and the current error path returns immediately after ending that folio.
This can leave the bio accumulated for earlier folios unsubmitted. Those folios then never receive read completion, and readers can wait indefinitely on the locked folios.
Route errors through the common out path so any pending bio is submitted before returning. Stop consuming more readahead folios once an error is seen, and only wait on and clear the current folio when it was actually added to the bio.
From the CVE record · Linux
The Linux kernel’s f2fs large-folio read path can leave a pending read unsubmitted if a later readahead folio encounters an error. Earlier folios may never complete, causing readers to wait indefinitely. The input does not establish an attacker path or specify network access, authentication, or user interaction requirements.
Engineers running Linux kernels that use f2fs should check their kernel versions; affected versions are not specified.