# CVE-2026-46175: f2fs: fix fsck inconsistency caused by FGGC of node block

> A flaw in the Linux kernel's f2fs filesystem causes fsck to misinterpret migrated node blocks, potentially leading to filesystem inconsistency and data corruption.

- **Severity:** High 7.1 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 28 May 2026
- **Updated:** 21 Oct 2026
- **Also known as:** AZL-88860, BELL-CVE-2026-46175, DEBIAN-CVE-2026-46175, GHSA-vwpg-8m6q-566g, ROOT-OS-DEBIAN-11-CVE-2026-46175, ROOT-OS-DEBIAN-12-CVE-2026-46175, ROOT-OS-DEBIAN-13-CVE-2026-46175, ROOT-OS-UBUNTU-2204-CVE-2026-46175, ROOT-OS-UBUNTU-2404-CVE-2026-46175, UBUNTU-CVE-2026-46175

## What is CVE-2026-46175?

CVE-2026-46175 is a high-severity vulnerability in Linux kernel, published on 28 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

## Which versions are affected by CVE-2026-46175?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2026-46175?

Apply the vendor's patch.

## Is CVE-2026-46175 being exploited?

There is no known exploitation of CVE-2026-46175 in the wild and no public exploit code.

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-46175 and fix it if it is affected.

What it is: CVE-2026-46175 is a high-severity vulnerability in Linux kernel, published on 28 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-46175 in the wild and no public exploit code.

Affected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-46175/ (Markdown: https://insights.sbomify.com/CVE-2026-46175/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-46175
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-46175
- OSV: https://osv.dev/vulnerability/CVE-2026-46175

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-46175/
Summaries are generated and may contain mistakes; the official description above is the record.