{"id":"CVE-2026-46175","title":"f2fs: fix fsck inconsistency caused by FGGC of node block","summary":"In the Linux kernel, the following vulnerability has been resolved:\n\nf2fs: fix fsck inconsistency caused by FGGC of node block\n\nDuring FGGC node block migration, fsck may incorrectly treat the\nmigrated node block as fsync-written data.\n\n…","severity":"high","cvss":7.1,"cvssVector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H","cvssSource":"cna","vendor":"Linux","product":"Linux","affected":["Linux >= da011cc0da8cf4a60ddf4d2ae8b42902a3d71e5f < d1820a5814eadb8e63ab6c7c8d04e28ce49836be","Linux >= da011cc0da8cf4a60ddf4d2ae8b42902a3d71e5f < 8ac93964658d0649337dcb3f6e38d77f8cdd86f3","Linux >= da011cc0da8cf4a60ddf4d2ae8b42902a3d71e5f < 8be551f538dc5b64183e27bd45a7a0795263f760","Linux >= da011cc0da8cf4a60ddf4d2ae8b42902a3d71e5f < e7c6d30169b03307d27c4479563df79c08f3a746","Linux >= da011cc0da8cf4a60ddf4d2ae8b42902a3d71e5f < c3e238bd1f56993f205ef83889d406dfeaf717a8","Linux 4.7"],"published":"2026-05-28","updated":"2026-10-21","sourceUpdated":"2026-10-21T12:41:23.769Z","source":"CVEORG","sourceUrl":"https://www.cve.org/CVERecord?id=CVE-2026-46175","references":[{"url":"https://git.kernel.org/stable/c/d1820a5814eadb8e63ab6c7c8d04e28ce49836be"},{"url":"https://git.kernel.org/stable/c/8ac93964658d0649337dcb3f6e38d77f8cdd86f3"},{"url":"https://git.kernel.org/stable/c/8be551f538dc5b64183e27bd45a7a0795263f760"},{"url":"https://git.kernel.org/stable/c/e7c6d30169b03307d27c4479563df79c08f3a746"},{"url":"https://git.kernel.org/stable/c/c3e238bd1f56993f205ef83889d406dfeaf717a8"}],"tags":["cve.org"],"epss":0.00169,"epssPercentile":0.05897,"ingestedAt":"2026-10-21T12:48:53.629Z","slug":"CVE-2026-46175","body":"## Overview\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nf2fs: fix fsck inconsistency caused by FGGC of node block\n\nDuring FGGC node block migration, fsck may incorrectly treat the\nmigrated node block as fsync-written data.\n\nThe reproduction scenario:\nroot@vm:/mnt/f2fs# seq 1 2048 | xargs -n 1 ./test_sync // write inline inode and sync\nroot@vm:/mnt/f2fs# rm -f 1\nroot@vm:/mnt/f2fs# sync\nroot@vm:/mnt/f2fs# f2fs_io gc_range // move data block in sync mode and not write CP\n  SPO, \"fsck --dry-run\" find inode has already checkpointed but still\n  with DENT_BIT_SHIFT set\n\nThe root cause is that GC does not clear the dentry mark and fsync mark\nduring node block migration, leading fsck to misinterpret them as\nuser-issued fsync writes.\n\nIn BGGC mode, node block migration is handled by f2fs_sync_node_pages(),\nwhich guarantees the dentry and fsync marks are cleared before writing.\n\nThis patch move the set/clear of the fsync|dentry marks into\n__write_node_folio to make the logic clearer, and ensures the\nfsync|dentry mark is cleared in FGGC.\n\n## Affected\n\n- `Linux >= da011cc0da8cf4a60ddf4d2ae8b42902a3d71e5f < d1820a5814eadb8e63ab6c7c8d04e28ce49836be`\n- `Linux >= da011cc0da8cf4a60ddf4d2ae8b42902a3d71e5f < 8ac93964658d0649337dcb3f6e38d77f8cdd86f3`\n- `Linux >= da011cc0da8cf4a60ddf4d2ae8b42902a3d71e5f < 8be551f538dc5b64183e27bd45a7a0795263f760`\n- `Linux >= da011cc0da8cf4a60ddf4d2ae8b42902a3d71e5f < e7c6d30169b03307d27c4479563df79c08f3a746`\n- `Linux >= da011cc0da8cf4a60ddf4d2ae8b42902a3d71e5f < c3e238bd1f56993f205ef83889d406dfeaf717a8`\n- `Linux 4.7`\n\n## Remediation\n\nRefer to the linked advisories for vendor-supplied fixes and affected version ranges.","depth":"twilight","depthScore":39,"depthScoreParts":{"impact":39.1,"likelihood":0,"exploitation":0,"ransomware":0},"changes":[]}