Kernel-level SMB (ksmbd) bug impacts Linux across environments; can crash kernels or enable escalation—broad impact, high-profile risk.
CVE-2026-64016
Kernel ksmbd use-after-free via SMB durable reconnect; crash or RCE risk.
Is CVE-2026-64016 being exploited?
Not confirmed. CVE-2026-64016 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.67% probability of exploitation in the next 30 days.
How severe is CVE-2026-64016?
CVE-2026-64016 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-64016?
Yes. A fix has been recorded for CVE-2026-64016. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-64016 affect?
CVE-2026-64016 affects Linux kernel (ksmbd - in-kernel SMB server), Any Linux distribution with ksmbd enabled. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-64016?
Apply vendor kernel security updates; disable ksmbd or block SMB (TCP 445) until patched.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote kernel use-after-free via SMB durable reconnect; can cause system crash (DoS) and may enable privilege escalation or remote code execution.
Immediate action required
- affected>= ce2e164c1c51c3f7813b80f8c926836e896bcbb3 and < a1a39f227c80cbf369767badc32cba2b225147d1
- affected>= 97a0cd55283b4e63fd92804da91c8d9896adcad9 and < 6cb0b9385320110fe24a5d5ac0000ade4bb3a3f3
- affected>= 1baff47b81f94f9231c91236aa511420d0e266b9 and < 3515503322f4819277091839eed46b695096aca5
- affected>= 6.18.33 and < 6.18.34
- affected>= 7.0.10 and < 7.0.11
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.