---
id: CVE-2026-46175
title: 'f2fs: fix fsck inconsistency caused by FGGC of node block'
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.

  …
severity: high
cvss: 7.1
cvssVector: 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H'
cvssSource: cna
vendor: Linux
product: Linux
affected:
  - >-
    Linux >= da011cc0da8cf4a60ddf4d2ae8b42902a3d71e5f <
    d1820a5814eadb8e63ab6c7c8d04e28ce49836be
  - >-
    Linux >= da011cc0da8cf4a60ddf4d2ae8b42902a3d71e5f <
    8ac93964658d0649337dcb3f6e38d77f8cdd86f3
  - >-
    Linux >= da011cc0da8cf4a60ddf4d2ae8b42902a3d71e5f <
    8be551f538dc5b64183e27bd45a7a0795263f760
  - >-
    Linux >= da011cc0da8cf4a60ddf4d2ae8b42902a3d71e5f <
    e7c6d30169b03307d27c4479563df79c08f3a746
  - >-
    Linux >= da011cc0da8cf4a60ddf4d2ae8b42902a3d71e5f <
    c3e238bd1f56993f205ef83889d406dfeaf717a8
  - Linux 4.7
published: '2026-05-28'
updated: '2026-10-21'
sourceUpdated: '2026-10-21T12:41:23.769Z'
source: CVEORG
sourceUrl: 'https://www.cve.org/CVERecord?id=CVE-2026-46175'
references:
  - url: 'https://git.kernel.org/stable/c/d1820a5814eadb8e63ab6c7c8d04e28ce49836be'
  - url: 'https://git.kernel.org/stable/c/8ac93964658d0649337dcb3f6e38d77f8cdd86f3'
  - url: 'https://git.kernel.org/stable/c/8be551f538dc5b64183e27bd45a7a0795263f760'
  - url: 'https://git.kernel.org/stable/c/e7c6d30169b03307d27c4479563df79c08f3a746'
  - url: 'https://git.kernel.org/stable/c/c3e238bd1f56993f205ef83889d406dfeaf717a8'
tags:
  - cve.org
epss: 0.00169
epssPercentile: 0.05897
ingestedAt: '2026-10-21T12:48:53.629Z'
---

## Overview

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.

## Affected

- `Linux >= da011cc0da8cf4a60ddf4d2ae8b42902a3d71e5f < d1820a5814eadb8e63ab6c7c8d04e28ce49836be`
- `Linux >= da011cc0da8cf4a60ddf4d2ae8b42902a3d71e5f < 8ac93964658d0649337dcb3f6e38d77f8cdd86f3`
- `Linux >= da011cc0da8cf4a60ddf4d2ae8b42902a3d71e5f < 8be551f538dc5b64183e27bd45a7a0795263f760`
- `Linux >= da011cc0da8cf4a60ddf4d2ae8b42902a3d71e5f < e7c6d30169b03307d27c4479563df79c08f3a746`
- `Linux >= da011cc0da8cf4a60ddf4d2ae8b42902a3d71e5f < c3e238bd1f56993f205ef83889d406dfeaf717a8`
- `Linux 4.7`

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.