CVE-2026-64016 is a memory-lifetime flaw in the Linux kernel's ksmbd SMB server implementation affecting durable-handle reconnect error handling. After a durable reconnect succeeds, ksmbd_reopen_durable_fd() republishes the same ksmbd_file object into the session volatile-ID table. If smb2_open() subsequently follows a later error path, cleanup performs ksmbd_fd_put(work, fp) and then unconditionally performs ksmbd_put_durable_fd(dh_info.fp). In the affected path, fp and dh_info.fp refer to the same ksmbd_file object. The first put drops the reconnect lookup reference, while the final durable put can invoke a non-session-aware close path that frees the file object without removing the volatile-ID entry that was just republished into the session table. This creates a stale session-table reference to freed memory, resulting in a use-after-free condition and an exploitable kernel memory-safety bug in ksmbd durable reconnect processing.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
1 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.