All vulnerabilities

Servers and applications

CVE-2026-53017

f2fs: fix data loss caused by incorrect use of nat_entry flag

Severity
Unrated
Published
24 Jun 2026
Last changed
30 Oct 2026
Added to UpHeron
30 Oct 2026
Fixed in
6.1.191, 6.6.160, 6.12.114, 6.18.57, 7.0.10
Exploit chance
0.2% in the next 30 daysHigher than 5% of CVEs. EPSS by FIRST, 19 Nov 2026
Sources
CVE Program

Description

In the Linux kernel, the following vulnerability has been resolved:

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.

From the CVE Program. Shortened; the full text is there.

Affected software

SoftwareAffected versions
Linux kernelServers and applications · cna:linux|linux
  • From 3.8 before 6.1.191
  • From 6.2 before 6.6.160
  • From 6.7 before 6.12.114
  • From 6.13 before 6.18.57
  • From 6.19 before 7.0.10

About Linux kernel

Unix-like operating system kernel, basis for all Linux operating systems

From Wikidata, CC0 1.0.
GitHub stars
255,726GitHub, 15 Nov 2026
Forks
67,394GitHub, 15 Nov 2026
Developer
Linus TorvaldsWikidata
License
GNU General Public License, version 2.0Wikidata
Written in
CWikidata
First released
25 Aug 1991Wikidata
First published on GitHub
4 Sept 2011GitHub

References

  • CVE.org https://www.cve.org/CVERecord?id=CVE-2026-53017