CVE-2026-53368

HIGHPre-NVD 7.17.1—
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
Trending — 4 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(medium)
EG Risk
37(Track)
EG Risk 37/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
3%
KEV
Not listed

Published

July 19, 2026

Last Modified

August 5, 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(6)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-oracle-7.0 (7.0.0-1008.8) @ resolute2026-09-07ubuntu
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-09-07ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1015.15) @ resolute2026-09-07ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1016.16) @ resolute2026-09-07ubuntu
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2016.16) @ resolute2026-09-07ubuntu
ubuntulinux-tools-gcp-edge (7.0.0-1011.11~24.04.1) @ noble2026-09-07ubuntu

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~rc7-1~exp1 (350 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (174 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.7-1~bpo13+1 (136 versions)7.0.7-1—

All Vendor Advisories

(6)

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 13× in last 7d / 117× 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 231 total refreshes for this CVE.

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

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 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-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 97.3% of all scored CVEs.
What is the CVSS score of CVE-2026-53368?
CVE-2026-53368 has a CVSS v4.0 base score of 7.1 (CNA self-assessment; NVD's own analysis pending).
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

See which npm, PyPI, Go, and Maven packages are affected by 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