CVE-2026-43330

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

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

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

A fix is available — apply it.

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

crypto: caam - fix overflow on long hmac keys

When a key longer than block size is supplied, it is copied and then hashed into the real key. The memory allocated for the copy needs to be rounded to DMA cache alignment, as otherwise the hashed key may corrupt neighbouring memory.

The copying is performed using kmemdup, however this leads to an overflow: reading more bytes (aligned_len - keylen) from the keylen source buffer. Fix this by replacing kmemdup with kmalloc, followed by memcpy.

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

Published

May 8, 2026

Last Modified

August 5, 2026

Advisory Details (5)

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

crypto: caam - fix overflow on long hmac keys - kernel/git/stable/linux.git - Linux kernel stable tree

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

crypto: caam - fix overflow on long hmac keys - kernel/git/stable/linux.git - Linux kernel stable tree

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

crypto: caam - fix overflow on long hmac keys - kernel/git/stable/linux.git - Linux kernel stable tree

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

crypto: caam - fix overflow on long hmac keys - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/80688afb9c35b3934ce2d6be9973758915e2e0ef
generic

crypto: caam - fix overflow on long hmac keys - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/31022cfde5235c45fa765f0aabeff5f0652852f2

Patch Availability(17)

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.85-1~bpo12+1 (17 versions)6.12.85-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.19~rc8-1~exp1 (125 versions)6.19.12-1

Weakness Classification(1)

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

Additional Vendor Advisories

(14)

Data Freshness Timeline

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

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

Frequently asked(5)

What is CVE-2026-43330?
CVE-2026-43330 is a high vulnerability published on May 8, 2026. In the Linux kernel, the following vulnerability has been resolved: crypto: caam - fix overflow on long hmac keys When a key longer than block size is supplied, it is copied and then hashed into the real key. The memory allocated for the copy needs to be rounded to DMA cache alignment, as otherwise…
When was CVE-2026-43330 disclosed?
CVE-2026-43330 was first published in the National Vulnerability Database on May 8, 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-43330 actively exploited?
CVE-2026-43330 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.1% of all scored CVEs.
What is the CVSS score of CVE-2026-43330?
CVE-2026-43330 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-43330?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-43330, 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-43330

Explore →

Is Your Infrastructure Affected by CVE-2026-43330?

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