Skip to content
Systems

CVE-2026-64142

9.8
Critical
EPSS 0.53%Patch availableJul 21, 2026

Use-after-free in Linux ksmbd durable-handle scavenger allowing kernel UAF.

common questions

Is CVE-2026-64142 being exploited?

Not confirmed. CVE-2026-64142 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.53% probability of exploitation in the next 30 days.

How severe is CVE-2026-64142?

CVE-2026-64142 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-64142?

Yes. A fix has been recorded for CVE-2026-64142. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-64142 affect?

CVE-2026-64142 affects Linux kernel (ksmbd SMB server module), Linux distributions shipping kernels with ksmbd enabled. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-64142?

Apply vendor/kernel patch immediately; limit SMB exposure and monitor logs.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Linux kernel (ksmbd SMB server module)Linux distributions shipping kernels with ksmbd enabled
impact

Remote SMB clients can trigger a kernel use-after-free via ksmbd durable-handle races, causing crashes/DoS and enabling potential privilege escalation or RCE.

action required

Immediate action required

affected versions
Linux Linux
  • affected>= 7f0cb478703cbeaddfe5c9101c5c73cd975d1073 and < 3a436932eb397e909d0607d76a8325abd9d85a35
  • affected>= d484d621d40f4a8b8959008802d79bef3609641b and < 95f072ef934ca00711d510676b8792cbf59a5aae
  • affected>= d484d621d40f4a8b8959008802d79bef3609641b and < 5da69a65b282d2276de22e5194ba0f88c836170c
  • affected>= d484d621d40f4a8b8959008802d79bef3609641b and < 1f8f3246d55f89350a1a67bdf3744b7241048e4e
  • affected>= d484d621d40f4a8b8959008802d79bef3609641b and < bf736184d063da1a552ffeff0481813599a182cc
  • affected6.11
vendor says fixed in< 6.11, >= 6.12.92 and <= 6.12.*, >= 6.18.34 and <= 6.18.*, >= 7.0.11 and <= 7.0.*, >= 7.1 and <= *

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.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free