{"id":14844,"date":"2026-09-04T19:02:14","date_gmt":"2026-09-04T11:02:14","guid":{"rendered":"https:\/\/www.54iter.cn\/?vuln=cve-2026-53368"},"modified":"2026-09-04T19:02:14","modified_gmt":"2026-09-04T11:02:14","slug":"cve-2026-53368","status":"publish","type":"vuln","link":"https:\/\/www.54iter.cn\/?vuln=cve-2026-53368","title":{"rendered":"CVE-2026-53368 [HIGH] &#8211; In the Linux kernel, the following vulnerability has been resolved:\n\nf2fs: fix fsck incons"},"content":{"rendered":"<p>In the Linux kernel, the following vulnerability has been resolved:<\/p>\n<p>f2fs: fix fsck inconsistency caused by incorrect nat_entry flag usage<\/p>\n<p>f2fs_need_dentry_mark() reads nat_entry flags without mutual exclusion<br \/>\nwith the checkpoint path, which can result in an incorrect inode block<br \/>\nmarking state. The scenario is as follows:<\/p>\n<p>create &amp; write &amp; fsync &#8216;file A&#8217;                 write checkpoint<br \/>\n&#8211; f2fs_do_sync_file \/\/ inline inode<br \/>\n &#8211; f2fs_write_inode \/\/ inode folio is dirty<br \/>\n                                                &#8211; f2fs_write_checkpoint<br \/>\n                                                 &#8211; f2fs_flush_merged_writes<br \/>\n                                                 &#8211; f2fs_sync_node_pages<br \/>\n &#8211; f2fs_fsync_node_pages \/\/ no dirty node<br \/>\n &#8211; f2fs_need_inode_block_update \/\/ return true<br \/>\n &#8211; f2fs_fsync_node_pages \/\/ inode dirtied<br \/>\n  &#8211; f2fs_need_dentry_mark \/\/return true<br \/>\n                                                 &#8211; f2fs_flush_nat_entries<br \/>\n                                                &#8211; f2fs_write_checkpoint end<br \/>\n  &#8211; __write_node_folio \/\/ inode with DENT_BIT_SHIFT set<br \/>\n  SPO, &#8220;fsck &#8211;dry-run&#8221; find inode has already checkpointed but still<br \/>\n  with DENT_BIT_SHIFT set<\/p>\n<p>The state observed by f2fs_need_dentry_mark() can differ from the state<br \/>\nobserved in __write_node_folio() after acquiring sbi-&gt;node_write. The<br \/>\nroot cause is that the semantics of IS_CHECKPOINTED and<br \/>\nHAS_FSYNCED_INODE are only guaranteed after the checkpoint write has<br \/>\nfully completed.<\/p>\n<p>This patch moves set_dentry_mark() into __write_node_folio() and<br \/>\nprotects it with the sbi-&gt;node_write lock.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>In the Linux kernel, the following vulnerability has been resolved:<\/p>\n<p>f2fs: fix fsck inconsistency caused by incorrect nat_entry flag usage<\/p>\n<p>f2fs_need_dentry_mark() reads nat_entry flags without mutual<\/p>\n","protected":false},"template":"","meta":[],"categories":[],"tags":[],"class_list":["post-14844","vuln","type-vuln","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/www.54iter.cn\/index.php?rest_route=\/wp\/v2\/vuln\/14844","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.54iter.cn\/index.php?rest_route=\/wp\/v2\/vuln"}],"about":[{"href":"https:\/\/www.54iter.cn\/index.php?rest_route=\/wp\/v2\/types\/vuln"}],"wp:attachment":[{"href":"https:\/\/www.54iter.cn\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=14844"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.54iter.cn\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=14844"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.54iter.cn\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=14844"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}