CVE-2026-53017

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.

• https://git.kernel.org/stable/c/20cedb4d9f6b230d0ee469690b8f868f06a07c29Patch
• https://git.kernel.org/stable/c/238e14eb7226f883b72caccd2d37bf5707df066bPatch

Published

Jun 24, 2026

Last Modified

Jul 15, 2026

Status

Analyzed

• How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
• Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
• PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
• AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.

• CVE-2026-53011In the Linux kernel, the following vulnerability has been re…7.8
• CVE-2026-53012In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2026-53013In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2026-53014In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2026-53015In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2026-53016In the Linux kernel, the following vulnerability has been re…7.8
• CVE-2026-53018In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2026-53019In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2026-5302CORS misconfiguration in CoolerControl/coolercontrold <4.0.0…8.1
• CVE-2026-53020In the Linux kernel, the following vulnerability has been re…7.8
• CVE-2026-53021In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2026-53022In the Linux kernel, the following vulnerability has been re…5.5