CVE-2026-53368

HIGHPre-NVD 7.17.1—
EchelonGraph scoreHIGH confidence

Score 7.1 from GitHub Security Advisory (severity: HIGH) published 2026-07-19. a secondary CVSS source baseline 7.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 5 sources updated this week
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 incorrect nat_entry flag usage

f2fs_need_dentry_mark() reads nat_entry flags without mutual exclusion with the checkpoint path, which can result in an incorrect inode block marking state. The scenario is as follows:

create & write & fsync 'file A' write checkpoint

  • f2fs_do_sync_file // inline inode
  • f2fs_write_inode // inode folio is dirty
  • f2fs_write_checkpoint
  • f2fs_flush_merged_writes
  • f2fs_sync_node_pages
  • f2fs_fsync_node_pages // no dirty node
  • f2fs_need_inode_block_update // return true
  • f2fs_fsync_node_pages // inode dirtied
  • f2fs_need_dentry_mark //return true
  • f2fs_flush_nat_entries
  • f2fs_write_checkpoint end
  • __write_node_folio // inode with DENT_BIT_SHIFT set
SPO, "fsck --dry-run" find inode has already checkpointed but still with DENT_BIT_SHIFT set

The state observed by f2fs_need_dentry_mark() can differ from the state observed in __write_node_folio() after acquiring sbi->node_write. The root cause is that the semantics of IS_CHECKPOINTED and HAS_FSYNCED_INODE are only guaranteed after the checkpoint write has fully completed.

This patch moves set_dentry_mark() into __write_node_folio() and protects it with the sbi->node_write lock.

CVSS v3
7.1
EG Score
7.1(high)
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

July 19, 2026

Last Modified

July 20, 2026

Advisory Details (3)

Auto-updated Jul 21, 2026
No patch confirmed yet.
generic

f2fs: fix fsck inconsistency caused by incorrect nat_entry flag usage - kernel/git/stable/linux.git - Linux kernel stable tree

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

f2fs: fix fsck inconsistency caused by incorrect nat_entry flag usage - kernel/git/stable/linux.git - Linux kernel stable tree

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

f2fs: fix fsck inconsistency caused by incorrect nat_entry flag usage - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/019f9dda7f66e55eb94cd32e1d3fff5835f73fbc

Vendor Advisories for CVE-2026-53368(2)

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

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-oracle-7.0 (7.0.0-1008.8) @ resolute2026-07-26ubuntu
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-07-26ubuntu

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.

All Vendor Advisories

(2)

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 18× in last 7d / 23× 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.

  1. 2026-07-27 10:07 UTCGHSA enrichment
  2. 2026-07-26 22:40 UTCVendor advisory
  3. 2026-07-26 22:40 UTCGHSA enrichment
  4. 2026-07-26 11:13 UTCEG score recompute
  5. 2026-07-26 11:13 UTCVendor advisory
  6. 2026-07-26 11:13 UTCGHSA enrichment
  7. 2026-07-25 14:18 UTCEPSS rescore
  8. 2026-07-24 14:18 UTCEPSS rescore
  9. 2026-07-23 14:18 UTCEPSS rescore
  10. 2026-07-23 03:19 UTCEG score recompute
  11. 2026-07-22 14:08 UTCEPSS rescore
  12. 2026-07-21 15:25 UTCEPSS rescore
  13. 2026-07-20 17:49 UTCEG score recompute
  14. 2026-07-20 17:48 UTCGHSA enrichment
  15. 2026-07-20 17:08 UTCEPSS rescore
  16. 2026-07-20 14:48 UTCEG score recompute▲ 7.10
  17. 2026-07-20 14:48 UTCGHSA enrichment
  18. 2026-07-20 14:32 UTCMITRE cvelistV5CVSS v3 → 7.1 · severity → HIGH
  19. 2026-07-19 14:31 UTCEPSS rescore
  20. 2026-07-19 14:31 UTCEPSS rescore
  21. 2026-07-19 10:25 UTCNVD update
  22. 2026-07-19 09:18 UTCEG score recompute
  23. 2026-07-19 09:17 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-53368?
CVE-2026-53368 is a high vulnerability published on July 19, 2026. In the Linux kernel, the following vulnerability has been resolved: f2fs: fix fsck inconsistency caused by incorrect nat_entry flag usage f2fsneeddentrymark() reads natentry flags without mutual exclusion with the checkpoint path, which can result in an incorrect inode block marking state. The…
When was CVE-2026-53368 disclosed?
CVE-2026-53368 was first published in the National Vulnerability Database on July 19, 2026, with the most recent update on July 20, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53368 actively exploited?
CVE-2026-53368 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 98.1% of all scored CVEs.
What is the CVSS score of CVE-2026-53368?
CVE-2026-53368 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-53368?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53368, 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

Explore the affected products and dependency analysis for CVE-2026-53368

Explore →

Is Your Infrastructure Affected by CVE-2026-53368?

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

Start Free Scan →Browse All CVEs