Skip to content
Cryptography

CVE-2026-64313

8.8
High
EPSS 0.35%Patch availableJul 27, 2026

Linux kernel ECC carry bug causes incorrect ECC operations.

common questions

Is CVE-2026-64313 being exploited?

Not confirmed. CVE-2026-64313 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.35% probability of exploitation in the next 30 days.

How severe is CVE-2026-64313?

CVE-2026-64313 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-64313?

Yes. A fix has been recorded for CVE-2026-64313. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-64313 affect?

CVE-2026-64313 affects Linux kernel (crypto/ecc.c), Distributions using affected kernel versions, Kernel consumers of ECDH/ECDSA (AF_ALG, TLS drivers). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-64313?

Install vendor kernel updates, reboot hosts, and update crypto-dependent services.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Linux kernel (crypto/ecc.c)Distributions using affected kernel versionsKernel consumers of ECDH/ECDSA (AF_ALG, TLS drivers)
impact

Faulty ECDH/ECDSA math can produce bad keys, cause signature verification failures, or enable cryptographic forgery/compromise of key material.

action required

Patch when possible

affected versions
Linux Linux
  • affected>= 3c4b23901a0c766879dff680cd6bdab47bcdbbd2 and < d11b2bb99bec1f5557c01cac42231e23745f49b8
  • affected>= 3c4b23901a0c766879dff680cd6bdab47bcdbbd2 and < b709e0e768766abe29a49e1c1922a1604be602f4
  • affected>= 3c4b23901a0c766879dff680cd6bdab47bcdbbd2 and < 24a54dfa06d09813b4802a374fad3d2c0e16a884
  • affected>= 3c4b23901a0c766879dff680cd6bdab47bcdbbd2 and < 677450e5ef850c4d28b7956aa01104548c2a894e
  • affected>= 3c4b23901a0c766879dff680cd6bdab47bcdbbd2 and < 5275e0fca256d081e2e7d4ba3dd8216c6e50d44e
  • affected>= 3c4b23901a0c766879dff680cd6bdab47bcdbbd2 and < 774ddddf5eb26eeca177350413e3e2bc50930ee9
  • affected>= 3c4b23901a0c766879dff680cd6bdab47bcdbbd2 and < ebaae7c4251cc0cdb2602f334d4f08a3e82d271e
  • affected>= 3c4b23901a0c766879dff680cd6bdab47bcdbbd2 and < 27b536a2ec8e2f85a0380c2d13c9ecbc7aaab406
  • affected4.8
vendor says fixed in< 4.8, >= 5.10.261 and <= 5.10.*, >= 5.15.212 and <= 5.15.*, >= 6.1.178 and <= 6.1.*, >= 6.6.145 and <= 6.6.*, >= 6.12.96 and <= 6.12.*, >= 6.18.39 and <= 6.18.*, >= 7.1.4 and <= 7.1.*, >= 7.2 and <= *

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free