CVE-2026-64313

HIGHPre-NVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-07-25. a secondary CVSS source baseline 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
8.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: 8.8Exploit: None knownExposed: 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:

crypto: ecc - Fix carry overflow in vli multiplication

The carry flag calculation fails when r01.m_high is saturated (0xFFFFFFFFFFFFFFFF) and addition of lower bits overflows.

The condition (r01.m_high < product.m_high) doesn't handle the case where r01.m_high == product.m_high and an additional carry exists from lower-bit overflow.

When commit 3c4b23901a0c ("crypto: ecdh - Add ECDH software support") introduced crypto/ecc.c, it split the muladd() function in the micro-ecc library into separate mul_64_64() and add_128_128() helpers. It seems the check got lost in translation.

Add proper handling for this boundary by accounting for the carry from the lower addition.

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

Published

July 25, 2026

Last Modified

August 17, 2026

Advisory Details (8)

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

crypto: ecc - Fix carry overflow in vli multiplication - kernel/git/stable/linux.git - Linux kernel stable tree

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

crypto: ecc - Fix carry overflow in vli multiplication - kernel/git/stable/linux.git - Linux kernel stable tree

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

crypto: ecc - Fix carry overflow in vli multiplication - kernel/git/stable/linux.git - Linux kernel stable tree

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

crypto: ecc - Fix carry overflow in vli multiplication - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/774ddddf5eb26eeca177350413e3e2bc50930ee9
generic

crypto: ecc - Fix carry overflow in vli multiplication - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/677450e5ef850c4d28b7956aa01104548c2a894e
generic

crypto: ecc - Fix carry overflow in vli multiplication - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5275e0fca256d081e2e7d4ba3dd8216c6e50d44e
generic

crypto: ecc - Fix carry overflow in vli multiplication - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/27b536a2ec8e2f85a0380c2d13c9ecbc7aaab406
generic

crypto: ecc - Fix carry overflow in vli multiplication - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/24a54dfa06d09813b4802a374fad3d2c0e16a884

Vendor Advisories for CVE-2026-64313(2)

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

Affected Packages

(6 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (55 versions)5.10.262-1—
linux-6.16.1.106-3~deb11u1 ... 6.1.177-1~deb11u1 (22 versions)6.1.180-1~deb11u1—
Debian:12(2)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (55 versions)6.1.180-1—
linux-6.12—6.12.100-1~deb12u1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.95-1~bpo12+1 (30 versions)6.12.96-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.1~rc7-1~exp1 (156 versions)7.1.4-1—

Data Freshness Timeline

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

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

Frequently asked(5)

What is CVE-2026-64313?
CVE-2026-64313 is a high vulnerability published on July 25, 2026. In the Linux kernel, the following vulnerability has been resolved: crypto: ecc - Fix carry overflow in vli multiplication The carry flag calculation fails when r01.m_high is saturated (0xFFFFFFFFFFFFFFFF) and addition of lower bits overflows. The condition (r01.mhigh < product.mhigh) doesn't…
When was CVE-2026-64313 disclosed?
CVE-2026-64313 was first published in the National Vulnerability Database on July 25, 2026, with the most recent update on August 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-64313 actively exploited?
CVE-2026-64313 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 71.8% of all scored CVEs.
What is the CVSS score of CVE-2026-64313?
CVE-2026-64313 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-64313?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64313, 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-64313

Explore →

Is Your Infrastructure Affected by CVE-2026-64313?

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

Start Free Scan →Browse All CVEs