The vulnerability stems from an inconsistency in the is_checkpointed flag during concurrent atomic commit and checkpoint writes in the Linux kernel’s f2fs file system. The flag can be left unset although the checkpoint write has completed, which may cause the filesystem to write the same data twice or leave state but not properly mark a node as checkpointed. This state mismatch can impair recovery procedures, leading to data loss or corruption when the system reboots or attempts to recover the filesystem.

The flaw exists in the f2fs implementation of the Linux kernel. Any system that uses the f2fs filesystem and is running a kernel version built from source before the patch is a potential target. All Linux kernel releases that include the f2fs driver before the fix are therefore affected.

The bug resides inside the kernel, so an attacker must generate conditions that trigger an atomic fsync while a checkpoint write is underway. The EPSS score is below 1 % and the vulnerability is not listed in the CISA KEV catalog, indicating a low to moderate exploitation likelihood. The impact is primarily local or privileged; there is no evidence of a remote code execution vector, but data integrity and system stability could be compromised.