CVE-2026-64450
Linux kernel TIPC out-of-bounds read enables kernel memory disclosure and crash.
Is CVE-2026-64450 being exploited?
Not confirmed. CVE-2026-64450 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.54% probability of exploitation in the next 30 days.
How severe is CVE-2026-64450?
CVE-2026-64450 is rated Critical with a CVSS score of 9.1. 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-64450?
Yes. A fix has been recorded for CVE-2026-64450. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-64450 affect?
CVE-2026-64450 affects Linux kernel with TIPC enabled, TIPC-enabled clusters, Linux distributions (kernel affected). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-64450?
Apply vendor/upstream kernel update or backport patch immediately.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote attacker can send crafted TIPC broadcast to trigger OOB kernel read, enabling kernel memory disclosure and kernel crash/DoS.
Immediate action required
- affected>= d7626b5acff9227e2a65da636a53e09bdafdc0aa and < 055663d21dc4336f67933ab26bef3c5934be6324
- affected>= d7626b5acff9227e2a65da636a53e09bdafdc0aa and < 016f5995c37a5a2c45198308f830f244517d70b7
- affected>= d7626b5acff9227e2a65da636a53e09bdafdc0aa and < 74b45af86a767594ba52330cd440ea84e24d700d
- affected>= d7626b5acff9227e2a65da636a53e09bdafdc0aa and < 9a51115fcdc78687c8852bf93a1db3951dbb223b
- affected>= d7626b5acff9227e2a65da636a53e09bdafdc0aa and < a21ed5064217cc33726da6c7ef1a520eba43aea1
- affected>= d7626b5acff9227e2a65da636a53e09bdafdc0aa and < 2de42e268174766cb2e2b90721afdfdff70e0d8d
- affected>= d7626b5acff9227e2a65da636a53e09bdafdc0aa and < f333b6851bdf326fd2134133272dbbed0c94d921
- affected>= d7626b5acff9227e2a65da636a53e09bdafdc0aa and < 2b66974a1b6134a4bbc3bfed181f7418f688eb54
- affected5.8
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.