CVE-2026-46175

*** Pendiente de traducción *** In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> f2fs: fix fsck inconsistency caused by FGGC of node block<br /> <br /> During FGGC node block migration, fsck may incorrectly treat the<br /> migrated node block as fsync-written data.<br /> <br /> The reproduction scenario:<br /> root@vm:/mnt/f2fs# seq 1 2048 | xargs -n 1 ./test_sync // write inline inode and sync<br /> root@vm:/mnt/f2fs# rm -f 1<br /> root@vm:/mnt/f2fs# sync<br /> root@vm:/mnt/f2fs# f2fs_io gc_range // move data block in sync mode and not write CP<br /> SPO, "fsck --dry-run" find inode has already checkpointed but still<br /> with DENT_BIT_SHIFT set<br /> <br /> The root cause is that GC does not clear the dentry mark and fsync mark<br /> during node block migration, leading fsck to misinterpret them as<br /> user-issued fsync writes.<br /> <br /> In BGGC mode, node block migration is handled by f2fs_sync_node_pages(),<br /> which guarantees the dentry and fsync marks are cleared before writing.<br /> <br /> This patch move the set/clear of the fsync|dentry marks into<br /> __write_node_folio to make the logic clearer, and ensures the<br /> fsync|dentry mark is cleared in FGGC.