CVE-2026-53017f2fs: fix data loss caused by incorrect use of nat_entry flag
- 5.5MediumCVSS base score
- 0.16%Exploitation in 30 daysEPSS · top 94% 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 data loss caused by incorrect use of nat_entry flag Data loss can occur when fsync is performed on a newly created file (before any checkpoint has been written) concurrently with a checkpoint operation. 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_flush_nat_entries - f2fs_fsync_node_pages // no dirty node - f2fs_need_inode_block_update // return false SPO and lost 'file A' f2fs_flush_nat_entries() sets the IS_CHECKPOINTED and HAS_LAST_FSYNC flags for the nat_entry, but this does not mean that the checkpoint has actually completed successfully. However, f2fs_need_inode_block_update() checks these flags and incorrectly assumes that the checkpoint has finished. The root cause is that the semantics of IS_CHECKPOINTED and HAS_LAST_FSYNC are only guaranteed after the checkpoint write fully completes. This patch modifies f2fs_need_inode_block_update() to acquire the sbi->node_write lock before reading the nat_entry flags, ensuring that once IS_CHECKPOINTED and HAS_LAST_FSYNC are observed to be set, the checkpoint operation has already completed.
Timeline
ID reserved
By Linux
- 15 days later
· 15 days later
Published
- 4 months later
· 4 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 |
|---|---|---|---|
| NVDNVD · Modified | 3.1 | Medium5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.16% · top 94% of all CVEs (12 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.
Affected products
- affected e05df3b115e7308afbca652769b54e4549fcc723 – < eb65e8c7bd0a78a470cbdd3ff96232ba4a2ace89
- affected e05df3b115e7308afbca652769b54e4549fcc723 – < 0645fa4d48e9b77d93f8b7a1c1fea58a97c2f8b0
- affected e05df3b115e7308afbca652769b54e4549fcc723 – < 9fd3bcb54a6afea5fa8a828d010561143560b7c5
- affected e05df3b115e7308afbca652769b54e4549fcc723 – < cb06a07d835ba1ea250785a796243bb483e65816
- affected e05df3b115e7308afbca652769b54e4549fcc723 – < 20cedb4d9f6b230d0ee469690b8f868f06a07c29
- affected e05df3b115e7308afbca652769b54e4549fcc723 – < 238e14eb7226f883b72caccd2d37bf5707df066b
- affected 3.8
- unaffected < 3.8
- unaffected 6.1.191 – ≤ 6.1.*
- unaffected 6.6.160 – ≤ 6.6.*
- unaffected 6.12.114 – ≤ 6.12.*
- unaffected 6.18.57 – ≤ 6.18.*
- unaffected 7.0.10 – ≤ 7.0.*
- unaffected 7.1 – ≤ *
References
References6
- https://git.kernel.org/stable/c/eb65e8c7bd0a78a470cbdd3ff96232ba4a2ace89 (opens in a new tab)
- https://git.kernel.org/stable/c/0645fa4d48e9b77d93f8b7a1c1fea58a97c2f8b0 (opens in a new tab)
- https://git.kernel.org/stable/c/9fd3bcb54a6afea5fa8a828d010561143560b7c5 (opens in a new tab)
- https://git.kernel.org/stable/c/cb06a07d835ba1ea250785a796243bb483e65816 (opens in a new tab)
- https://git.kernel.org/stable/c/20cedb4d9f6b230d0ee469690b8f868f06a07c29 (opens in a new tab)
- https://git.kernel.org/stable/c/238e14eb7226f883b72caccd2d37bf5707df066b (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-38885 (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-53017)Record last updated .