CVE-2026-46175

HIGHPre-NVD 7.17.1—
EchelonGraph scoreMEDIUM confidence

Score 7.1 from GitHub Security Advisory (severity: HIGH) published 2026-05-28. the CNA's CVSS baseline 7.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
7.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.1Exploit: None knownExposed: 0

A fix is available — apply it.

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.

CVSS v3
7.1
EG Score
7.1(medium)
EG Risk
36(Track)
EG Risk 36/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity71% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
2%
KEV
Not listed

Published

May 28, 2026

Last Modified

August 5, 2026

Advisory Details (3)

Auto-updated Jun 12, 2026
No patch confirmed yet.
generic

f2fs: fix fsck inconsistency caused by FGGC of node block - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/e7c6d30169b03307d27c4479563df79c08f3a746
generic

f2fs: fix fsck inconsistency caused by FGGC of node block - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/c3e238bd1f56993f205ef83889d406dfeaf717a8
generic

f2fs: fix fsck inconsistency caused by FGGC of node block - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8be551f538dc5b64183e27bd45a7a0795263f760

Vendor Advisories for CVE-2026-46175(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(8)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1016.16) @ resolute2026-08-25ubuntu
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-28.28) @ resolute2026-08-25ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1009.9) @ resolute2026-08-25ubuntu
ubuntulinux-virtual-hwe-24.04-edge (7.0.0-28.28~24.04.1) @ noble2026-08-25ubuntu
ubuntulinux-tools-oracle-7.0 (7.0.0-1008.8) @ resolute2026-08-25ubuntu
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-08-25ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1015.15) @ resolute2026-08-25ubuntu
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2016.16) @ resolute2026-08-25ubuntu

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 7.2~rc5-1~exp1 (496 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 7.2~rc5-1~exp1 (335 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.2~rc5-1~exp1 (160 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.7-1~bpo13+1 (133 versions)7.0.7-1—

All Vendor Advisories

(8)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 5× in last 7d / 86× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 258 total refreshes for this CVE.

  1. 2026-09-04 05:06 UTCEPSS rescore
  2. 2026-09-02 14:12 UTCEPSS rescore
  3. 2026-09-01 13:54 UTCEPSS rescore
  4. 2026-08-30 19:17 UTCEPSS rescore
  5. 2026-08-30 01:22 UTCEPSS rescore
  6. 2026-08-28 21:41 UTCEPSS rescore
  7. 2026-08-27 14:25 UTCEPSS rescore
  8. 2026-08-25 13:49 UTCEPSS rescore
  9. 2026-08-25 04:52 UTCEG score recompute
  10. 2026-08-25 04:52 UTCVendor advisory
  11. 2026-08-25 04:51 UTCGHSA enrichment
  12. 2026-08-23 14:41 UTCEG score recompute
  13. 2026-08-23 14:41 UTCVendor advisory
  14. 2026-08-23 14:41 UTCGHSA enrichment
  15. 2026-08-23 00:19 UTCEPSS rescore
  16. 2026-08-21 23:49 UTCEPSS rescore
  17. 2026-08-21 15:33 UTCEG score recompute
  18. 2026-08-21 15:33 UTCVendor advisory
  19. 2026-08-21 15:33 UTCGHSA enrichment
  20. 2026-08-20 22:55 UTCEPSS rescore
  21. 2026-08-20 21:51 UTCVendor advisory
  22. 2026-08-20 21:51 UTCGHSA enrichment
  23. 2026-08-20 10:55 UTCEG score recompute
  24. 2026-08-20 10:55 UTCVendor advisory
  25. 2026-08-20 10:55 UTCGHSA enrichment
Show 75 more
  1. 2026-08-19 17:04 UTCEPSS rescore
  2. 2026-08-18 13:48 UTCEPSS rescore
  3. 2026-08-17 13:47 UTCEPSS rescore
  4. 2026-08-17 08:55 UTCVendor advisory
  5. 2026-08-17 08:55 UTCGHSA enrichment
  6. 2026-08-16 15:11 UTCEG score recompute
  7. 2026-08-16 15:11 UTCVendor advisory
  8. 2026-08-16 15:11 UTCGHSA enrichment
  9. 2026-08-16 14:56 UTCEPSS rescore
  10. 2026-08-16 02:36 UTCEG score recompute
  11. 2026-08-16 02:36 UTCVendor advisory
  12. 2026-08-16 02:36 UTCGHSA enrichment
  13. 2026-08-16 02:14 UTCEPSS rescore
  14. 2026-08-15 01:30 UTCEPSS rescore
  15. 2026-08-14 23:03 UTCVendor advisory
  16. 2026-08-14 23:03 UTCGHSA enrichment
  17. 2026-08-14 12:07 UTCVendor advisory
  18. 2026-08-14 12:07 UTCGHSA enrichment
  19. 2026-08-14 01:11 UTCEG score recompute
  20. 2026-08-14 01:11 UTCVendor advisory
  21. 2026-08-14 01:11 UTCGHSA enrichment
  22. 2026-08-13 22:00 UTCEPSS rescore
  23. 2026-08-13 08:02 UTCVendor advisory
  24. 2026-08-13 08:02 UTCGHSA enrichment
  25. 2026-08-12 20:26 UTCEG score recompute
  26. 2026-08-12 20:26 UTCVendor advisory
  27. 2026-08-12 20:26 UTCGHSA enrichment
  28. 2026-08-12 13:51 UTCEPSS rescore
  29. 2026-08-12 09:30 UTCVendor advisory
  30. 2026-08-12 09:30 UTCGHSA enrichment
  31. 2026-08-11 22:16 UTCEG score recompute
  32. 2026-08-11 22:16 UTCVendor advisory
  33. 2026-08-11 22:16 UTCGHSA enrichment
  34. 2026-08-11 11:18 UTCVendor advisory
  35. 2026-08-11 11:18 UTCGHSA enrichment
  36. 2026-08-11 00:07 UTCEG score recompute
  37. 2026-08-11 00:07 UTCVendor advisory
  38. 2026-08-11 00:06 UTCGHSA enrichment
  39. 2026-08-11 00:00 UTCEPSS rescore
  40. 2026-08-10 05:04 UTCVendor advisory
  41. 2026-08-10 05:04 UTCGHSA enrichment
  42. 2026-08-09 18:09 UTCEG score recompute
  43. 2026-08-09 18:09 UTCVendor advisory
  44. 2026-08-09 18:09 UTCGHSA enrichment
  45. 2026-08-09 13:46 UTCEPSS rescore
  46. 2026-08-09 07:13 UTCVendor advisory
  47. 2026-08-09 07:13 UTCGHSA enrichment
  48. 2026-08-08 20:17 UTCVendor advisory
  49. 2026-08-08 20:17 UTCGHSA enrichment
  50. 2026-08-08 09:04 UTCVendor advisory
  51. 2026-08-08 09:04 UTCGHSA enrichment
  52. 2026-08-07 22:08 UTCVendor advisory
  53. 2026-08-07 22:08 UTCGHSA enrichment
  54. 2026-08-07 11:12 UTCVendor advisory
  55. 2026-08-07 11:12 UTCGHSA enrichment
  56. 2026-08-07 00:07 UTCEG score recompute
  57. 2026-08-07 00:07 UTCVendor advisory
  58. 2026-08-07 00:07 UTCGHSA enrichment
  59. 2026-08-06 13:47 UTCEPSS rescore
  60. 2026-08-06 11:45 UTCVendor advisory
  61. 2026-08-06 11:45 UTCGHSA enrichment
  62. 2026-08-06 00:37 UTCEG score recompute
  63. 2026-08-06 00:37 UTCVendor advisory
  64. 2026-08-06 00:37 UTCGHSA enrichment
  65. 2026-08-05 19:17 UTCEPSS rescore
  66. 2026-08-05 13:41 UTCVendor advisory
  67. 2026-08-05 13:41 UTCGHSA enrichment
  68. 2026-08-04 23:59 UTCEG score recompute
  69. 2026-08-04 23:59 UTCVendor advisory
  70. 2026-08-04 23:59 UTCGHSA enrichment
  71. 2026-08-04 15:10 UTCEPSS rescore
  72. 2026-08-04 10:39 UTCEPSS rescore
  73. 2026-08-04 03:14 UTCVendor advisory
  74. 2026-08-04 03:14 UTCGHSA enrichment
  75. 2026-08-03 16:14 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-46175?
CVE-2026-46175 is a high vulnerability published on May 28, 2026. 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…
When was CVE-2026-46175 disclosed?
CVE-2026-46175 was first published in the National Vulnerability Database on May 28, 2026, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-46175 actively exploited?
CVE-2026-46175 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 97.6% of all scored CVEs.
What is the CVSS score of CVE-2026-46175?
CVE-2026-46175 has a CVSS v4.0 base score of 7.1 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-46175?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-46175, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-46175

Explore →

Is Your Infrastructure Affected by CVE-2026-46175?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs