CVE-2026-64016
CriticalIn the Linux kernel, the following vulnerability has been resolved: ksmbd: fix durable reconnect error path file lifetime After a durable reconnect succeeds, ksmbd_reopen_durable_fd() republishes the same ksmbd_file into the session volatile-id table. If smb2_open() then takes a later error path, cleanup first calls ksmbd_fd_put(work, fp) and then unconditionally calls ksmbd_put_durable_fd(dh_info.fp). In this case fp and dh_info.fp are the same object. The first put drops the reconnect lookup reference, but the final durable put can run __ksmbd_close_fd(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 dh_info.fp, keep using the durable-only put path.
CVSS 3.1 score
9.8
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Affected versions
Linux kernel versions
6.18.33,
7.0.10
and later are affected. Fixed in
6.18.34,
7.0.11
and their respective stable series.
References
3 totalFrequently asked questions
-
What is CVE-2026-64016?
CVE-2026-64016 is a Critical severity Linux kernel vulnerability with a CVSS score of 9.8 out of 10 . It affects Linux kernel versions from 6.18.33 onward and has been patched in 6.18.34 and 7.0.11. CVE-2026-64016 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.
-
What is the CVSS score for CVE-2026-64016?
CVE-2026-64016 has a CVSS score of 9.8 out of 10, rated Critical severity (CVSS 3.1). The vector string is
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. -
Is there a patch available for CVE-2026-64016?
Yes. CVE-2026-64016 has been patched. Fixed versions include 6.18.34 and 7.0.11. If you are running Linux kernel 6.18.33 or later up to the fix versions, apply the relevant patch for your kernel branch.
-
Is CVE-2026-64016 actively exploited?
No. CVE-2026-64016 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.