f2fs: fix fsck inconsistency caused by FGGC of node block
CVE-2026-46175 · published 28 May 2026
How serious is it
- Severity: high, CVSS score 7.1 out of 10.
- No exploit prediction (EPSS) score yet.
- Not on the CISA list of exploited vulnerabilities.
- No public exploit in Exploit-DB.
Is your app affected by CVE-2026-46175?
Paste this prompt into Claude Code, Cursor or any AI coding tool: it runs a free Shippable scan of your project and fixes what it finds. Built with Lovable, Bolt or v0? Scan your live app. Or upload your package file.
Who is affected
- Linux Linux: da011cc0da8cf4a60ddf4d2ae8b42902a3d71e5f to < d1820a5814eadb8e63ab6c7c8d04e28ce49836be, da011cc0da8cf4a60ddf4d2ae8b42902a3d71e5f to < 8ac93964658d0649337dcb3f6e38d77f8cdd86f3, da011cc0da8cf4a60ddf4d2ae8b42902a3d71e5f to < 8be551f538dc5b64183e27bd45a7a0795263f760, da011cc0da8cf4a60ddf4d2ae8b42902a3d71e5f to < e7c6d30169b03307d27c4479563df79c08f3a746
- Linux Linux: 4.7
How to check
- Find out whether you run the affected product and which version, then compare it with the versions above.
How to fix
Copies a prompt for Claude Code, Cursor or Codex that asks it to check whether you run this product.
- Apply the vendor's update or mitigation from the references below. If there is none yet, limit exposure of the affected service until there is.
- If a vulnerable version was live, check your logs and rotate the secrets that server could read.
The advisory
In the Linux kernel, the following vulnerability has been resolved:
f2fs: fix fsck inconsistency caused by FGGC of node block
During FGGC node block migration, fsck may incorrectly treat the
migrated node block as fsync-written data.
The reproduction scenario:
root@vm:/mnt/f2fs# seq 1 2048 | xargs -n 1 ./test_sync // write inline inode and sync
root@vm:/mnt/f2fs# rm -f 1
root@vm:/mnt/f2fs# sync
root@vm:/mnt/f2fs# f2fs_io gc_range // move data block in sync mode and not write CP
SPO, "fsck --dry-run" find inode has already checkpointed but still
with DENT_BIT_SHIFT set
The root cause is that GC does not clear the dentry mark and fsync mark
during node block migration, leading fsck to misinterpret them as
user-issued fsync writes.
In BGGC mode, node block migration is handled by f2fs_sync_node_pages(),
which guarantees the dentry and fsync marks are cleared before writing.
This patch move the set/clear of the fsync|dentry marks into
__write_node_folio to make the logic clearer, and ensures the
fsync|dentry mark is cleared in FGGC.
Check your whole app
Dependencies are only half of it. Free and read-only: before you push, run npx shippable-dev scan localhost:3000 in your project folder, no account needed. For your live app, you prove it's yours with a one-line tag first.
References
- git.kernel.org/stable/c/d1820a5814eadb8e63ab6c7c8d04e28ce49836be
- git.kernel.org/stable/c/8ac93964658d0649337dcb3f6e38d77f8cdd86f3
- git.kernel.org/stable/c/8be551f538dc5b64183e27bd45a7a0795263f760
- git.kernel.org/stable/c/e7c6d30169b03307d27c4479563df79c08f3a746
- git.kernel.org/stable/c/c3e238bd1f56993f205ef83889d406dfeaf717a8
Merged from CVE List. Last updated 25 Oct 2026. All vulnerabilities · RSS · JSON