CVE-2026-53368f2fs: fix fsck inconsistency caused by incorrect nat_entry flag usage
- 7.1HighCVSS base score
- 0.17%Exploitation in 30 daysEPSS · top 93% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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. The scenario is as follows: create & write & fsync 'file A' write checkpoint - f2fs_do_sync_file // inline inode - f2fs_write_inode // inode folio is dirty - f2fs_write_checkpoint - f2fs_flush_merged_writes - f2fs_sync_node_pages - f2fs_fsync_node_pages // no dirty node - f2fs_need_inode_block_update // return true - f2fs_fsync_node_pages // inode dirtied - f2fs_need_dentry_mark //return true - f2fs_flush_nat_entries - f2fs_write_checkpoint end - __write_node_folio // inode with DENT_BIT_SHIFT set SPO, "fsck --dry-run" find inode has already checkpointed but still with DENT_BIT_SHIFT set The state observed by f2fs_need_dentry_mark() can differ from the state observed in __write_node_folio() after acquiring sbi->node_write. The root cause is that the semantics of IS_CHECKPOINTED and HAS_FSYNCED_INODE are only guaranteed after the checkpoint write has fully completed. This patch moves set_dentry_mark() into __write_node_folio() and protects it with the sbi->node_write lock.
Timeline
ID reserved
By Linux
- 40 days later
· 40 days later
Published
- 3 months later
· 3 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | High7.1 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H |
| NVDNVD · Modified | 3.1 | High7.1 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H |
- EPSS (exploitation in 30 days)
- 0.17% · top 93% of all CVEs (14 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.1.
Affected products
- affected 88bd02c9472a166b706284a34a84f1243322d782 – < bb1275802b482bc5854e434e212589fe253eab22
- affected 88bd02c9472a166b706284a34a84f1243322d782 – < 270c519bca3a59b6140d176415aff16e4e06f9e3
- affected 88bd02c9472a166b706284a34a84f1243322d782 – < bedb710b63ae1bd617e65d0a8cf6cea1200b3753
- affected 88bd02c9472a166b706284a34a84f1243322d782 – < b28a83ea4934215b5de906c3ee4fbfbc651573e0
- affected 88bd02c9472a166b706284a34a84f1243322d782 – < 019f9dda7f66e55eb94cd32e1d3fff5835f73fbc
- affected 3.18
- unaffected < 3.18
- unaffected 6.1.191 – ≤ 6.1.*
- unaffected 6.12.114 – ≤ 6.12.*
- unaffected 6.18.30 – ≤ 6.18.*
- unaffected 7.0.7 – ≤ 7.0.*
- unaffected 7.1 – ≤ *
References
References5
- https://git.kernel.org/stable/c/bb1275802b482bc5854e434e212589fe253eab22 (opens in a new tab)
- https://git.kernel.org/stable/c/270c519bca3a59b6140d176415aff16e4e06f9e3 (opens in a new tab)
- https://git.kernel.org/stable/c/bedb710b63ae1bd617e65d0a8cf6cea1200b3753 (opens in a new tab)
- https://git.kernel.org/stable/c/b28a83ea4934215b5de906c3ee4fbfbc651573e0 (opens in a new tab)
- https://git.kernel.org/stable/c/019f9dda7f66e55eb94cd32e1d3fff5835f73fbc (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-45438 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-53368)Record last updated .