Affects the Linux kernel TLS path used broadly across servers and network devices; CVSS 9.8 and can cause kernel memory corruption/DoS or RCE, impacting enterprise infrastructure.
CVE-2026-64046
Linux kernel TLS scatterlist bug can corrupt kernel memory via crafted TLS packets.
Is CVE-2026-64046 being exploited?
Not confirmed. CVE-2026-64046 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.51% probability of exploitation in the next 30 days.
How severe is CVE-2026-64046?
CVE-2026-64046 is rated Critical with a CVSS score of 9.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-64046?
Yes. A fix has been recorded for CVE-2026-64046. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-64046 affect?
CVE-2026-64046 affects Linux kernel (net/tls subsystem), Distributions with kTLS enabled (Ubuntu, RHEL, Debian, SUSE, etc.), Network appliances using upstream Linux kernel TLS. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-64046?
Apply vendor kernel updates ASAP or disable kTLS until patched.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Crafted TLS records targeting kTLS can trigger kernel memory corruption, causing crashes, denial of service, or potential remote code execution.
Immediate action required
- affected>= 9aaaa56845a06aeabdd597cbe19492dc01f281ec and < 49a5faaa471ddcd37b6893970c9916eb836e7c31
- affected>= 9aaaa56845a06aeabdd597cbe19492dc01f281ec and < 91359966e247c0244c66d50bbb8e74aefa4321c3
- affected>= 9aaaa56845a06aeabdd597cbe19492dc01f281ec and < 410351158dfef2d67fea6603680b3a6013c6ed9d
- affected>= 9aaaa56845a06aeabdd597cbe19492dc01f281ec and < acdc12b71c9aa4be5dcd2c8062753c6d2033e235
- affected>= 9aaaa56845a06aeabdd597cbe19492dc01f281ec and < 929b1548e63ac72e104c07d8ee8cbbeeba2fa89a
- affected>= 9aaaa56845a06aeabdd597cbe19492dc01f281ec and < af855f4c966afafef74faf8390c7b86568c0d46d
- affected>= 9aaaa56845a06aeabdd597cbe19492dc01f281ec and < b9c015ef1a7bf1e8dc67f21c6381f36deb2c3a36
- affected>= 9aaaa56845a06aeabdd597cbe19492dc01f281ec and < ff26a0e8377dec07e4a7230db7675bed1b9a6d03
- affectedd529d6c9f7e3aaeac13c4948f79799ccb825f29d
- affected>= 5.4.14 and < 5.5
- affected5.5
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.