PT-2026-44298 · Linux · Linux

Published 2026-05-28 · Updated 2026-05-28 · CVE-2026-46175

NVD

CVSS v3.1

7.1

High

Base vector

AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H

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.

Fix

Related Identifiers

CVE-2026-46175

Affected Products

Linux

References · 4

• https://nvd.nist.gov/vuln/detail/CVE-2026-46175 · Security Note
• https://git.kernel.org/stable/c/c3e238bd1f56993f205ef83889d406dfeaf717a8 · Note
• https://git.kernel.org/stable/c/8be551f538dc5b64183e27bd45a7a0795263f760 · Note
• https://git.kernel.org/stable/c/e7c6d30169b03307d27c4479563df79c08f3a746 · Note