{"id":82238,"date":"2026-07-19T12:47:01","date_gmt":"2026-07-19T09:17:01","guid":{"rendered":"https:\/\/afaghhosting.net\/blog\/cve-2026-53368-f2fs-fix-fsck-inconsistency-caused-by-incorrect-nat_entry-flag-usage\/"},"modified":"2026-07-19T12:47:01","modified_gmt":"2026-07-19T09:17:01","slug":"cve-2026-53368-f2fs-fix-fsck-inconsistency-caused-by-incorrect-nat_entry-flag-usage","status":"publish","type":"post","link":"https:\/\/afaghhosting.net\/blog\/cve-2026-53368-f2fs-fix-fsck-inconsistency-caused-by-incorrect-nat_entry-flag-usage\/","title":{"rendered":"CVE-2026-53368 &#8211; f2fs: fix fsck inconsistency caused by incorrect nat_entry flag usage"},"content":{"rendered":"<p>CVE ID :CVE-2026-53368<\/p>\n<p>  Published : July 19, 2026, 9:17 a.m. | 23\u00a0minutes ago<\/p>\n<p>  Description :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<p>  Severity: 0.0 | NA<\/p>\n<p>  Visit the link for more details, such as CVSS details, affected products, timeline, and more&#8230;\u00a0<\/p>\n","protected":false},"excerpt":{"rendered":"<p>CVE ID :CVE-2026-53368 Published : July 19, 2026, 9:17 a.m. | 23\u00a0minutes ago Description :In the Linux kernel, the following vulnerability has been resolved: f2fs: fix fsck inconsistency caused by incorrect nat_entry flag usage f2fs_need_dentry_mark() reads nat_entry flags without mutual exclusion with the checkpoint path, which can result in an incorrect inode block marking state. &hellip;<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[26],"tags":[],"class_list":["post-82238","post","type-post","status-publish","format-standard","hentry","category-vulnerability"],"_links":{"self":[{"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/posts\/82238","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/comments?post=82238"}],"version-history":[{"count":0,"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/posts\/82238\/revisions"}],"wp:attachment":[{"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/media?parent=82238"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/categories?post=82238"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/tags?post=82238"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}