CVE-2026-46175 json
f2fs: fix fsck inconsistency caused by FGGC of node block
published 2026-05-28 5 mo ago modified 2026-10-30 10 d ago also EUVD-2026-32802
- cvss
- 7.1
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.1%
- EPSS 0.1% chance of exploitation in 30 days, percentile 2%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- Linux Linux 6.1.191, 6.6.160, 6.12.114, 6.18.30, 7.0.7, 7.1
- linux Debian 13 6.12.115-2
- linux Debian 14 7.0.7-1
debian advisories DEBIAN-CVE-2026-46175
- linux Ubuntu 26.04 LTS 7.0.0-28.28
- linux-aws Ubuntu 26.04 LTS 7.0.0-1009.9
- linux-gcp Ubuntu 26.04 LTS 7.0.0-1008.8
- linux-gke Ubuntu 26.04 LTS 7.0.0-1003.4
- linux-ibm Ubuntu 26.04 LTS 7.0.0-1010.10
- linux-azure Ubuntu 26.04 LTS 7.0.0-1010.10
- linux-raspi Ubuntu 26.04 LTS 7.0.0-1015.15
- linux-riscv Ubuntu 26.04 LTS 7.0.0-28.28.1
ubuntu advisories UBUNTU-CVE-2026-46175
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- kernel-source openSUSE Tumbleweed 7.0.11-1.1
opensuse advisories openSUSE-SU-2026:10954-1
- git.kernel.org/stable/c/3b7a0bbb3444addddb139f42a74ab4492052fa27 commit
- git.kernel.org/stable/c/d1820a5814eadb8e63ab6c7c8d04e28ce49836be commit
- git.kernel.org/stable/c/8ac93964658d0649337dcb3f6e38d77f8cdd86f3 commit
- git.kernel.org/stable/c/8be551f538dc5b64183e27bd45a7a0795263f760 commit
- git.kernel.org/stable/c/e7c6d30169b03307d27c4479563df79c08f3a746 commit
- git.kernel.org/stable/c/c3e238bd1f56993f205ef83889d406dfeaf717a8 commit
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-46175 updated
kernel: f2fs: fix fsck inconsistency caused by FGGC of node block
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernelnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.13% chance of exploitation in the next 30 days, higher than 2% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.1 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H |
Affected products
- Linux Linux
Classification
- Technology feeds
References
- git.kernel.org /stable/c/3b7a0bbb3444addddb139f42a74ab4492052fa27
- git.kernel.org /stable/c/d1820a5814eadb8e63ab6c7c8d04e28ce49836be
- git.kernel.org /stable/c/8ac93964658d0649337dcb3f6e38d77f8cdd86f3
-
git.kernel.org
/stable/c/8be551f538dc5b64183e27bd45a7a0795263f760
patch
-
git.kernel.org
/stable/c/e7c6d30169b03307d27c4479563df79c08f3a746
patch
-
git.kernel.org
/stable/c/c3e238bd1f56993f205ef83889d406dfeaf717a8
patch
Sources
- CVE List CVE-2026-46175
- NVD CVE-2026-46175
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.