CVE-2026-53029

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-06-24. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

fs/ntfs3: prevent uninitialized lcn caused by zero len

syzbot reported a uninit-value in ntfs_iomap_begin [1].

Since runs was not touched yet, run_lookup_entry() immediately fails and returns false, which makes the value of "*len" 0. Simultaneously, the new value and err value are also 0, causing the logic in attr_data_get_block_locked() to jump directly to ok, ultimately resulting in *lcn being triggered before it is set [1].

In ntfs_iomap_begin(), the check for a 0 value in clen is moved forward to before updating lcn to avoid this [1].

[1] BUG: KMSAN: uninit-value in ntfs_iomap_begin+0x8c0/0x1460 fs/ntfs3/inode.c:825 ntfs_iomap_begin+0x8c0/0x1460 fs/ntfs3/inode.c:825 iomap_iter+0x9b7/0x1540 fs/iomap/iter.c:110

Local variable lcn created at: ntfs_iomap_begin+0x15d/0x1460 fs/ntfs3/inode.c:786

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
29(Track)
EG Risk 29/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
Severity55% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
4%
KEV
Not listed

Published

June 24, 2026

Last Modified

July 15, 2026

Advisory Details (2)

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

fs/ntfs3: prevent uninitialized lcn caused by zero len - kernel/git/stable/linux.git - Linux kernel stable tree

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

fs/ntfs3: prevent uninitialized lcn caused by zero len - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/485f750cac3d8bdf5552a0e3d79ce5e3a03ece49

Vendor Advisories for CVE-2026-53029(1)

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

Patch Availability(8)

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

(1 across 1 ecosystem)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (137 versions)7.0.10-1

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(8)

Data Freshness Timeline

(refreshed 20× in last 7d / 96× 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 157 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-53029?
CVE-2026-53029 is a medium vulnerability published on June 24, 2026. In the Linux kernel, the following vulnerability has been resolved: fs/ntfs3: prevent uninitialized lcn caused by zero len syzbot reported a uninit-value in ntfsiomapbegin [1]. Since runs was not touched yet, runlookupentry() immediately fails and returns false, which makes the value of "*len" 0.…
When was CVE-2026-53029 disclosed?
CVE-2026-53029 was first published in the National Vulnerability Database on June 24, 2026, with the most recent update on July 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53029 actively exploited?
CVE-2026-53029 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 96.1% of all scored CVEs.
What is the CVSS score of CVE-2026-53029?
CVE-2026-53029 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-53029?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53029, 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-53029

Explore →

Is Your Infrastructure Affected by CVE-2026-53029?

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