CVE-2026-43245

HIGHNVD 7.57.5
EchelonGraph scoreMEDIUM confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-05-06. NVD baseline CVSS 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.5EG
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.5Exploit: None knownExposed: 0

A fix is available — apply it.

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

ntfs: ->d_compare() must not block

... so don't use __getname() there. Switch it (and ntfs_d_hash(), while we are at it) to kmalloc(PATH_MAX, GFP_NOWAIT). Yes, ntfs_d_hash() almost certainly can do with smaller allocations, but let ntfs folks deal with that - keep the allocation size as-is for now.

Stop abusing names_cachep in ntfs, period - various uses of that thing in there have nothing to do with pathnames; just use k[mz]alloc() and be done with that. For now let's keep sizes as-in, but AFAICS none of the users actually want PATH_MAX.

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

Published

May 6, 2026

Last Modified

August 5, 2026

Advisory Details (3)

Auto-updated May 11, 2026
No patch confirmed yet.
generic

ntfs: ->d_compare() must not block - kernel/git/stable/linux.git - Linux kernel stable tree

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

ntfs: ->d_compare() must not block - kernel/git/stable/linux.git - Linux kernel stable tree

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

ntfs: ->d_compare() must not block - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/142c444a395f4d26055c8a4473e228bb86283f1e

Vendor Advisories for CVE-2026-43245(1)

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

Patch Availability(15)

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

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.94-1~bpo12+1 (27 versions)6.12.94-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.19~rc8-1~exp1 (113 versions)6.19.6-1

All Vendor Advisories

(14)

Data Freshness Timeline

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

Frequently asked(5)

What is CVE-2026-43245?
CVE-2026-43245 is a high vulnerability published on May 6, 2026. In the Linux kernel, the following vulnerability has been resolved: ntfs: ->d_compare() must not block ... so don't use getname() there. Switch it (and ntfsdhash(), while we are at it) to kmalloc(PATHMAX, GFPNOWAIT). Yes, ntfsdhash() almost certainly can do with smaller allocations, but let ntfs…
When was CVE-2026-43245 disclosed?
CVE-2026-43245 was first published in the National Vulnerability Database on May 6, 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-43245 actively exploited?
CVE-2026-43245 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 63.1% of all scored CVEs.
What is the CVSS score of CVE-2026-43245?
CVE-2026-43245 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-43245?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-43245, 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-43245

Explore →

Is Your Infrastructure Affected by CVE-2026-43245?

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