Linux kernel vulnerability impacts widespread server, cloud, and network devices; can cause kernel corruption and compromise infrastructure.
CVE-2026-64047
Linux kernel TLS off-by-one in scatterlist causes kernel memory corruption
Is CVE-2026-64047 being exploited?
Not confirmed. CVE-2026-64047 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-64047?
CVE-2026-64047 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-64047?
Yes. A fix has been recorded for CVE-2026-64047. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-64047 affect?
CVE-2026-64047 affects Linux kernel (net/tls sk_msg scatterlist), Servers, cloud hosts, network appliances running affected kernels. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-64047?
Apply vendor kernel patches and reboot impacted systems immediately.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Out-of-bounds scatterlist chain in net/tls can corrupt kernel memory, causing crashes (DoS) or enabling privilege escalation/arbitrary kernel code execution.
Immediate action required
- affected>= 9aaaa56845a06aeabdd597cbe19492dc01f281ec and < 73963a375885d5ccb7def39fd0b4f542e0f343dd
- affected>= 9aaaa56845a06aeabdd597cbe19492dc01f281ec and < 47110c3a9ac247b688657337f5981efcfcb240dc
- affected>= 9aaaa56845a06aeabdd597cbe19492dc01f281ec and < 84158c2997159df4a0d70cd9c46774512d32a522
- affected>= 9aaaa56845a06aeabdd597cbe19492dc01f281ec and < 131ef12057d92b77b636321b7849c69222405a97
- affected>= 9aaaa56845a06aeabdd597cbe19492dc01f281ec and < 66339b71f105e6f83e0da3b9583d95077534fe1d
- affected>= 9aaaa56845a06aeabdd597cbe19492dc01f281ec and < eca989eab4b2599dcb02f72140a7c08f08838520
- affected>= 9aaaa56845a06aeabdd597cbe19492dc01f281ec and < 2fb0dc7e0099686c4e9d2732745d8a31b18c3628
- affected>= 9aaaa56845a06aeabdd597cbe19492dc01f281ec and < 285943c6e7ca309bbea84b253745154241d9788a
- 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.