CVE-2026-46175: f2fs: fix fsck inconsistency caused by FGGC of node block
f2fs: fix fsck inconsistency caused by FGGC of node block
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Linux kernel f2fsto a version that resolves this vulnerability.Patch f2fs: fix fsck inconsistency caused by FGGC of node block - Compensating control
Avoid running node block migration on FGGC until the fix is applied, since the bug can make “fsck --dry-run” misinterpret migrated node blocks as fsync-written data due to uncleared dentry/fsync marks.
Event History
Frequently Asked Questions
What is the severity of CVE-2026-46175?
The severity of CVE-2026-46175 is high with a score of 7.1.
How do I fix CVE-2026-46175?
To fix CVE-2026-46175, upgrade to the latest version of the Linux kernel that includes the patch for this vulnerability.
What systems are affected by CVE-2026-46175?
CVE-2026-46175 affects systems running the f2fs file system in the Linux kernel.
What is the impact of CVE-2026-46175?
The impact of CVE-2026-46175 includes potential data corruption during the FGGC node block migration.
How can I mitigate the risks of CVE-2026-46175 before applying a fix?
To mitigate risks from CVE-2026-46175, avoid using the f2fs file system until the upgrade can be performed.