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.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.5Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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)
EPSS
35.6%
KEV
Not listed

Published

May 6, 2026

Last Modified

May 23, 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.

Data Freshness Timeline

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

  1. 2026-07-15 16:57 UTCEPSS rescore
  2. 2026-07-15 02:00 UTCEPSS rescore
  3. 2026-07-13 22:30 UTCEPSS rescore
  4. 2026-07-13 06:13 UTCEPSS rescore
  5. 2026-07-12 05:46 UTCEPSS rescore
  6. 2026-07-11 08:27 UTCEPSS rescore
  7. 2026-07-09 19:10 UTCEPSS rescore
  8. 2026-07-08 15:16 UTCEPSS rescore
  9. 2026-07-07 13:46 UTCEPSS rescore
  10. 2026-07-06 16:27 UTCEPSS rescore
  11. 2026-07-06 02:23 UTCEPSS rescore
  12. 2026-07-05 02:30 UTCEPSS rescore
  13. 2026-07-04 06:31 UTCEPSS rescore
  14. 2026-07-01 15:06 UTCEPSS rescore
  15. 2026-06-30 23:22 UTCEPSS rescore
  16. 2026-06-28 14:07 UTCEPSS rescore
  17. 2026-06-28 04:56 UTCEPSS rescore
  18. 2026-06-27 03:08 UTCEPSS rescore
  19. 2026-06-25 13:49 UTCEPSS rescore
  20. 2026-06-25 13:49 UTCEPSS rescore
  21. 2026-06-24 14:05 UTCEPSS rescore
  22. 2026-06-23 21:33 UTCEPSS rescore
  23. 2026-06-22 14:25 UTCEPSS rescore
  24. 2026-06-22 14:25 UTCEPSS rescore
  25. 2026-06-21 14:56 UTCEPSS rescore
Show 75 more
  1. 2026-06-21 14:56 UTCEPSS rescore
  2. 2026-06-21 01:59 UTCEPSS rescore
  3. 2026-06-19 19:25 UTCEPSS rescore
  4. 2026-06-18 17:52 UTCEPSS rescore
  5. 2026-06-18 17:52 UTCEPSS rescore
  6. 2026-06-17 17:53 UTCEPSS rescore
  7. 2026-06-16 17:52 UTCEPSS rescore
  8. 2026-06-15 17:49 UTCEPSS rescore
  9. 2026-06-15 05:28 UTCEG score recompute
  10. 2026-06-15 05:28 UTCGHSA enrichment
  11. 2026-06-14 18:34 UTCEG score recompute
  12. 2026-06-14 18:34 UTCGHSA enrichment
  13. 2026-06-14 07:33 UTCEG score recompute
  14. 2026-06-14 07:33 UTCGHSA enrichment
  15. 2026-06-13 23:00 UTCEPSS rescore
  16. 2026-06-12 23:55 UTCEG score recompute
  17. 2026-06-12 23:55 UTCGHSA enrichment
  18. 2026-06-12 23:12 UTCEPSS rescore
  19. 2026-06-12 23:12 UTCEPSS rescore
  20. 2026-06-12 06:23 UTCEG score recompute
  21. 2026-06-12 06:23 UTCGHSA enrichment
  22. 2026-06-11 19:29 UTCEG score recompute
  23. 2026-06-11 19:29 UTCGHSA enrichment
  24. 2026-06-11 14:00 UTCEPSS rescore
  25. 2026-06-11 08:36 UTCEG score recompute
  26. 2026-06-11 08:36 UTCGHSA enrichment
  27. 2026-06-10 22:18 UTCEPSS rescore
  28. 2026-06-10 20:56 UTCEG score recompute
  29. 2026-06-10 20:56 UTCGHSA enrichment
  30. 2026-06-10 13:22 UTCEPSS rescore
  31. 2026-06-10 13:22 UTCEPSS rescore
  32. 2026-06-10 09:55 UTCEG score recompute
  33. 2026-06-10 09:55 UTCGHSA enrichment
  34. 2026-06-09 23:02 UTCEG score recompute
  35. 2026-06-09 23:02 UTCGHSA enrichment
  36. 2026-06-09 09:38 UTCEG score recompute
  37. 2026-06-09 09:38 UTCGHSA enrichment
  38. 2026-06-08 22:13 UTCEG score recompute
  39. 2026-06-08 22:13 UTCGHSA enrichment
  40. 2026-06-08 14:17 UTCEPSS rescore
  41. 2026-06-08 14:17 UTCEPSS rescore
  42. 2026-06-08 05:59 UTCEG score recompute
  43. 2026-06-08 05:59 UTCGHSA enrichment
  44. 2026-06-07 19:06 UTCEG score recompute
  45. 2026-06-07 19:06 UTCGHSA enrichment
  46. 2026-06-07 15:25 UTCEPSS rescore
  47. 2026-06-07 15:25 UTCEPSS rescore
  48. 2026-06-07 08:12 UTCEG score recompute
  49. 2026-06-07 08:12 UTCGHSA enrichment
  50. 2026-06-06 21:19 UTCEG score recompute
  51. 2026-06-06 21:19 UTCGHSA enrichment
  52. 2026-06-06 13:47 UTCEPSS rescore
  53. 2026-06-06 13:47 UTCEPSS rescore
  54. 2026-06-06 10:03 UTCEG score recompute
  55. 2026-06-06 10:03 UTCGHSA enrichment
  56. 2026-06-05 22:59 UTCEG score recompute
  57. 2026-06-05 22:59 UTCGHSA enrichment
  58. 2026-06-05 22:47 UTCEPSS rescore
  59. 2026-06-05 11:56 UTCEG score recompute
  60. 2026-06-05 11:56 UTCGHSA enrichment
  61. 2026-06-05 06:10 UTCEPSS rescore
  62. 2026-06-05 06:10 UTCEPSS rescore
  63. 2026-06-05 01:03 UTCEG score recompute
  64. 2026-06-05 01:03 UTCGHSA enrichment
  65. 2026-06-04 14:01 UTCEG score recompute
  66. 2026-06-04 14:01 UTCGHSA enrichment
  67. 2026-06-04 13:12 UTCEPSS rescore
  68. 2026-06-04 13:12 UTCEPSS rescore
  69. 2026-06-04 03:07 UTCEG score recompute
  70. 2026-06-04 03:07 UTCGHSA enrichment
  71. 2026-06-03 16:12 UTCEG score recompute
  72. 2026-06-03 16:12 UTCGHSA enrichment
  73. 2026-06-03 05:18 UTCEG score recompute
  74. 2026-06-03 05:18 UTCGHSA enrichment
  75. 2026-06-02 20: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 May 23, 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 35.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
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

Explore the affected products and dependency analysis for 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.