Answer in brief
CVE-2026-46175 records a Unknown severity vulnerability in f2fs: fix fsck inconsistency caused by FGGC of node block. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=da011cc0da8cf4a60ddf4d2ae8b42902a3d71e5f <8be551f538dc5b64183e27bd45a7a0795263f760 || >=da011cc0da8cf4a60ddf4d2ae8b42902a3d71e5f <e7c6d30169b03307d27c4479563df79c08f3a746 || >=da011cc0da8cf4a60ddf4d2ae8b42902a3d71e5f <c3e238bd1f56993f205ef83889d406dfeaf717a8 | 8be551f538dc5b64183e27bd45a7a0795263f760, e7c6d30169b03307d27c4479563df79c08f3a746, c3e238bd1f56993f205ef83889d406dfeaf717a8 |
| Linux/Linuxgeneric | 4.7 | Not reported |
Published upstream
May 28, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-46175 records a Unknown severity vulnerability in f2fs: fix fsck inconsistency caused by FGGC of node block. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=da011cc0da8cf4a60ddf4d2ae8b42902a3d71e5f <8be551f538dc5b64183e27bd45a7a0795263f760 || >=da011cc0da8cf4a60ddf4d2ae8b42902a3d71e5f <e7c6d30169b03307d27c4479563df79c08f3a746 || >=da011cc0da8cf4a60ddf4d2ae8b42902a3d71e5f <c3e238bd1f56993f205ef83889d406dfeaf717a8 | 8be551f538dc5b64183e27bd45a7a0795263f760, e7c6d30169b03307d27c4479563df79c08f3a746, c3e238bd1f56993f205ef83889d406dfeaf717a8 |
| Linux/Linuxgeneric | 4.7 | Not reported |
Published upstream
May 28, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.