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

A fix is available — apply it.

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
29%
KEV
Not listed

Published

July 25, 2026

Last Modified

September 3, 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.

Patch Availability(6)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-nvidia-tegra-rt-6.8 (6.8.0-1035.38) @ noble2026-09-20ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1019.19) @ resolute2026-09-20ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1013.13) @ resolute2026-09-20ubuntu
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-31.31) @ resolute2026-09-20ubuntu
ubuntulinux-tools-gcp-edge (7.0.0-1011.11~24.04.1) @ noble2026-09-20ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1018.18~24.04.1) @ noble2026-09-20ubuntu

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

(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 (158 versions)7.1.4-1—

Weakness Classification(1)

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

Additional Vendor Advisories

(6)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

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

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

Related CVEs(same vendor + same CWE)

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 September 3, 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 70.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