{"id":"CVE-2026-53368","title":"In the Linux kernel, the following vulnerability has been resolved:\n\nf2fs: fix fsck inconsistency caused by incorrect nat_entry flag usage\n\nf2fs_need_dentry_mark() reads nat_entry flags without mutual exclusion\nwith the checkpoint path, …","summary":"In the Linux kernel, the following vulnerability has been resolved:\n\nf2fs: fix fsck inconsistency caused by incorrect nat_entry flag usage\n\nf2fs_need_dentry_mark() reads nat_entry flags without mutual exclusion\nwith the checkpoint path, …","severity":"high","published":"2026-07-19","updated":"2026-07-19","source":"NVD","sourceUrl":"https://nvd.nist.gov/vuln/detail/CVE-2026-53368","references":[{"url":"https://git.kernel.org/stable/c/019f9dda7f66e55eb94cd32e1d3fff5835f73fbc","label":"416baaa9-dc9f-4396-8d5f-8c081fb06d67"},{"url":"https://git.kernel.org/stable/c/b28a83ea4934215b5de906c3ee4fbfbc651573e0","label":"416baaa9-dc9f-4396-8d5f-8c081fb06d67"},{"url":"https://git.kernel.org/stable/c/bedb710b63ae1bd617e65d0a8cf6cea1200b3753","label":"416baaa9-dc9f-4396-8d5f-8c081fb06d67"},{"url":"https://git.kernel.org/stable/c/270c519bca3a59b6140d176415aff16e4e06f9e3"}],"tags":["nvd","cve.org"],"epss":0.00171,"epssPercentile":0.06435,"ingestedAt":"2026-07-19T14:31:07.160Z","vendor":"Linux","product":"Linux","affected":["Linux >= 88bd02c9472a166b706284a34a84f1243322d782 < 270c519bca3a59b6140d176415aff16e4e06f9e3","Linux >= 88bd02c9472a166b706284a34a84f1243322d782 < bedb710b63ae1bd617e65d0a8cf6cea1200b3753","Linux >= 88bd02c9472a166b706284a34a84f1243322d782 < b28a83ea4934215b5de906c3ee4fbfbc651573e0","Linux >= 88bd02c9472a166b706284a34a84f1243322d782 < 019f9dda7f66e55eb94cd32e1d3fff5835f73fbc","Linux 3.18"],"cvss":7.1,"cvssVector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H","cvssSource":"cna","slug":"CVE-2026-53368","body":"## Overview\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nf2fs: fix fsck inconsistency caused by incorrect nat_entry flag usage\n\nf2fs_need_dentry_mark() reads nat_entry flags without mutual exclusion\nwith the checkpoint path, which can result in an incorrect inode block\nmarking state. The scenario is as follows:\n\ncreate & write & fsync 'file A'                 write checkpoint\n- f2fs_do_sync_file // inline inode\n - f2fs_write_inode // inode folio is dirty\n                                                - f2fs_write_checkpoint\n                                                 - f2fs_flush_merged_writes\n                                                 - f2fs_sync_node_pages\n - f2fs_fsync_node_pages // no dirty node\n - f2fs_need_inode_block_update // return true\n - f2fs_fsync_node_pages // inode dirtied\n  - f2fs_need_dentry_mark //return true\n                                                 - f2fs_flush_nat_entries\n                                                - f2fs_write_checkpoint end\n  - __write_node_folio // inode with DENT_BIT_SHIFT set\n  SPO, \"fsck --dry-run\" find inode has already checkpointed but still\n  with DENT_BIT_SHIFT set\n\nThe state observed by f2fs_need_dentry_mark() can differ from the state\nobserved in __write_node_folio() after acquiring sbi->node_write. The\nroot cause is that the semantics of IS_CHECKPOINTED and\nHAS_FSYNCED_INODE are only guaranteed after the checkpoint write has\nfully completed.\n\nThis patch moves set_dentry_mark() into __write_node_folio() and\nprotects it with the sbi->node_write lock.\n\n## Remediation\n\nRefer to the linked advisories for vendor-supplied fixes and affected version ranges.","depth":"twilight","depthScore":39,"depthScoreParts":{"impact":39.1,"likelihood":0,"exploitation":0,"ransomware":0},"changes":[{"seq":227200,"id":"CVE-2026-53368","ts":1792587052868,"field":"cvss","old":null,"new":"7.1"},{"seq":227199,"id":"CVE-2026-53368","ts":1792587052868,"field":"severity","old":"none","new":"high"}]}