CVE-2026-53017 f2fs: fix data loss caused by incorrect use of nat_entry flag

Medium 5.5 Published Updated

A race condition in the Linux kernel f2fs filesystem can cause data loss when fsyncing a new file concurrently with a checkpoint operation.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Local or same network only
Victim action needed
Not needed
Fix
Available

What is CVE-2026-53017?

CVE-2026-53017 is a medium-severity vulnerability in Linux kernel, published on 24 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.

Official 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.

Which versions are affected by CVE-2026-53017?

It affects 1 product.

Products include Linux kernel.

How do I fix CVE-2026-53017?

Apply the vendor's patch.

Is CVE-2026-53017 being exploited?

There is no known exploitation of CVE-2026-53017 in the wild and no public exploit code.

All Linux kernel vulnerabilities

Sources

Also known as BELL-CVE-2026-53017, DEBIAN-CVE-2026-53017, GHSA-f2m7-5m7m-7g2c, ROOT-OS-DEBIAN-11-CVE-2026-53017, ROOT-OS-DEBIAN-12-CVE-2026-53017, ROOT-OS-DEBIAN-13-CVE-2026-53017 and 3 more.

Is CVE-2026-53017 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free