CVE-2026-46175f2fs: fix fsck inconsistency caused by FGGC of node block
- 7.1HighCVSS base score
- 0.13%Exploitation in 30 daysEPSS · top 98% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
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.
Timeline
ID reserved
By Linux
- 15 days later
· 15 days later
Published
- 5 months later
· 5 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | High7.1 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H |
| NVDNVD · Modified | 3.1 | High7.1 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H |
- EPSS (exploitation in 30 days)
- 0.13% · top 98% of all CVEs (12 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.1.
Affected products
- affected da011cc0da8cf4a60ddf4d2ae8b42902a3d71e5f – < 3b7a0bbb3444addddb139f42a74ab4492052fa27
- affected da011cc0da8cf4a60ddf4d2ae8b42902a3d71e5f – < d1820a5814eadb8e63ab6c7c8d04e28ce49836be
- affected da011cc0da8cf4a60ddf4d2ae8b42902a3d71e5f – < 8ac93964658d0649337dcb3f6e38d77f8cdd86f3
- affected da011cc0da8cf4a60ddf4d2ae8b42902a3d71e5f – < 8be551f538dc5b64183e27bd45a7a0795263f760
- affected da011cc0da8cf4a60ddf4d2ae8b42902a3d71e5f – < e7c6d30169b03307d27c4479563df79c08f3a746
- affected da011cc0da8cf4a60ddf4d2ae8b42902a3d71e5f – < c3e238bd1f56993f205ef83889d406dfeaf717a8
- affected 4.7
- unaffected < 4.7
- unaffected 6.1.191 – ≤ 6.1.*
- unaffected 6.6.160 – ≤ 6.6.*
- unaffected 6.12.114 – ≤ 6.12.*
- unaffected 6.18.30 – ≤ 6.18.*
- unaffected 7.0.7 – ≤ 7.0.*
- unaffected 7.1 – ≤ *
References
References6
- https://git.kernel.org/stable/c/3b7a0bbb3444addddb139f42a74ab4492052fa27 (opens in a new tab)
- https://git.kernel.org/stable/c/d1820a5814eadb8e63ab6c7c8d04e28ce49836be (opens in a new tab)
- https://git.kernel.org/stable/c/8ac93964658d0649337dcb3f6e38d77f8cdd86f3 (opens in a new tab)
- https://git.kernel.org/stable/c/8be551f538dc5b64183e27bd45a7a0795263f760 (opens in a new tab)
- https://git.kernel.org/stable/c/e7c6d30169b03307d27c4479563df79c08f3a746 (opens in a new tab)
- https://git.kernel.org/stable/c/c3e238bd1f56993f205ef83889d406dfeaf717a8 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-32802 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-46175)Record last updated .