CVE-2026-64541
Linux kernel SMC-R use-after-free allows kernel crash and possible privilege escalation.
Is CVE-2026-64541 being exploited?
Not confirmed. CVE-2026-64541 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.56% probability of exploitation in the next 30 days.
How severe is CVE-2026-64541?
CVE-2026-64541 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-64541?
Yes. A fix has been recorded for CVE-2026-64541. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-64541 affect?
CVE-2026-64541 affects Linux kernel (SMC-R feature). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-64541?
Apply vendor kernel patches for SMC-R immediately and reboot affected hosts.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
UAF in SMC-R receive handler can trigger kernel panic (remote/local DoS) and may enable kernel memory corruption leading to privilege escalation or RCE.
Immediate action required
- affected>= d7b0e37c1ac152905b18a5b9506179091a35b0b6 and < 8de4f665d0febfb92803dece377791a563fc7041
- affected>= d7b0e37c1ac152905b18a5b9506179091a35b0b6 and < 8145b432136285e01091815b48ceb2dae261f262
- affected>= d7b0e37c1ac152905b18a5b9506179091a35b0b6 and < 1951bffbc6493ec34cff3956b29d4bc6606904a6
- affected>= d7b0e37c1ac152905b18a5b9506179091a35b0b6 and < 647b19e5cc145a2f1f685ae8ff3805a17356888c
- affected>= d7b0e37c1ac152905b18a5b9506179091a35b0b6 and < 472e9d7c0d5b03be3ff91ff941f57da822b031bc
- affected>= d7b0e37c1ac152905b18a5b9506179091a35b0b6 and < 3bfb96d9bc6a7ed0b99c7db329cc2e22a28d84bb
- affected>= d7b0e37c1ac152905b18a5b9506179091a35b0b6 and < ce5aa8084329351086894aa34d77e40301d5bd3d
- affected>= d7b0e37c1ac152905b18a5b9506179091a35b0b6 and < 9d160b35cc34a2ba8229d07651468a7848325135
- affected4.18
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.