CVE-2026-64016: ksmbd: fix durable reconnect error path file lifetime
In the Linux kernel, the following vulnerability has been resolved:
ksmbd: fix durable reconnect error path file lifetime
After a durable reconnect succeeds, ksmbdreopendurablefd() republishes the same ksmbdfile into the session volatile-id table. If smb2open() then takes a later error path, cleanup first calls ksmbdfdput(work, fp) and then unconditionally calls ksmbdputdurablefd(dhinfo.fp).
In this case fp and dhinfo.fp are the same object. The first put drops the reconnect lookup reference, but the final durable put can run ksmbdclosefd(NULL, fp). Because the final close is not session-aware, it can free the file object without removing the volatile-id entry that was just published into the session table.
Use the session-aware put for the final reconnect drop when the reconnect had already succeeded and the error path is cleaning up the republished file. Earlier reconnect failures, before fp is assigned to dhinfo.fp, keep using the durable-only put path.
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2026-64016?
CVE-2026-64016 has a severity rating of 42.
How do I fix CVE-2026-64016?
To fix CVE-2026-64016, ensure you update the Linux kernel to the latest patched version.
What systems are affected by CVE-2026-64016?
CVE-2026-64016 affects systems running the affected versions of the Linux kernel with ksmbd enabled.
What type of vulnerability is CVE-2026-64016?
CVE-2026-64016 is related to the ksmbd file handling during error paths.
When was CVE-2026-64016 published?
CVE-2026-64016 was published on July 19, 2026.