f2fs: fix to avoid potential deadloop in f2fs_fsync_node_pages()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 608514deba38c8611ad330d6a3c8e2b9a1f68e4b · < ce366bfa821ec81dd45bde547ee31e659306cc61| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
f2fs: fix to avoid potential deadloop in f2fs_fsync_node_pages()
There is potential deadloop in race condition:
Thread A Thread B - fsync - f2fs_do_sync_file - f2fs_fsync_node_pages - last_fsync_dnode - folio_get(last_folio) - f2fs_setattr - f2fs_truncate - f2fs_truncate_blocks - f2fs_do_truncate_blocks - f2fs_truncate_inode_blocks - truncate_dnode - truncate_node - invalidate_mapping_pages - folio->mapping = NULL - is_node_folio alwasy return false - atomic && !marked is always true, then goto retry
From the CVE record · Linux
A race between fsync and truncate in the Linux kernel's f2fs filesystem can cause f2fs_fsync_node_pages() to loop indefinitely. The input does not specify whether an attacker can trigger this, or any authentication or user-interaction requirements.
Engineers running Linux systems that use f2fs should check their kernels; affected versions are not specified.