f2fs: fix to avoid potential deadloop in f2fs_fsync_node_pages()
- 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.6.160, 6.12.114, 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: 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
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 608514deba38c8611ad330d6a3c8e2b9a1f68e4b · fixed in 58ca9f06480457eb9c9513e1ae2b75316d4ed1e5; From 608514deba38c8611ad330d6a3c8e2b9a1f68e4b · fixed in bdc06381d590ad5833ee7a2c56b8b685d80ee9b5; From 608514deba38c8611ad330d6a3c8e2b9a1f68e4b · fixed in 161513f53e4ac90fd356433bdf8e31e6adeb92af; From 608514deba38c8611ad330d6a3c8e2b9a1f68e4b · fixed in 905411f6504876d268ba8dafc8e75367782da4b7; From 608514deba38c8611ad330d6a3c8e2b9a1f68e4b · fixed in ce366bfa821ec81dd45bde547ee31e659306cc61
- Linux Linux
4.7
- KernelLinux
From 4.7.0 · fixed in 6.6.160; From 6.7.0 · fixed in 6.12.114; From 6.13.0 · fixed in 6.18.51; From 6.19.0 · fixed in 7.2.5