← All Advisories
Reported from OT-Advisories.com as of

CVE-2026-46175

Last refreshed2026-10-23

Status: UPDATED  |  Advisory ID: CVE-2026-46175

Key Details

CVECVE-2026-46175
CVSS Score / Version
7.1 (High) / CVSS v3.1
Updated2026-10-21
CVSS Vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
CVSS Prose
attack vector is local; attack complexity is low; privileges required is low; user interaction is none; scope is unchanged; confidentiality impact is none; integrity impact is high; availability impact is high.
Affected products
Linux Kernel

Affected Products, Subsystems & Sectors

VendorProductAffected VersionsPatch Status
LinuxLinux Kernel
SubsystemsOT Supporting Infrastructure
SectorsAll Sectors

What to Know

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. (NVD)

What to Do

Monitor Linux's web page for any future patch releases.

References

SourceReference
NVDhttps://nvd.nist.gov/vuln/detail/CVE-2026-46175
CVEhttps://www.cve.org/CVERecord?id=CVE-2026-46175
Report compilation © 2026 OT-Advisories.com  ·  CC BY 4.0  ·  Source materials remain the property of their respective publishers as cited.