CVEvulnerability
CVE-2026-64016
9.8 CRITICAL
Official page ↗
- Status
- Analyzed
- Published
- 2026-07-19
- Last modified
- 2026-10-13
- Assigner
- 416baaa9-dc9f-4396-8d5f-8c081fb06d67
- CVSS 3.1 (416baaa9-dc9f-4396-8d5f-8c081fb06d67)
- 9.8 CRITICAL — CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- Weaknesses
- CWE-416
Description
In 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.
Affected configurations
• linux linux kernel 6.18.33
• linux linux kernel 7.0.10
• linux linux kernel 7.1
Related
Weakness · CWE (1)
- CWE-416 Use After Free weakness
References
- https://git.kernel.org/stable/c/3515503322f4819277091839eed46b695096aca5 Patch
- https://git.kernel.org/stable/c/478bfaa036bd0c7e179acff8b8484bccdee3b8c7 Patch
- https://git.kernel.org/stable/c/5e641e4ee0bc1937408d41051a908ad4151be63b Patch
- https://git.kernel.org/stable/c/6cb0b9385320110fe24a5d5ac0000ade4bb3a3f3 Patch
- https://git.kernel.org/stable/c/a1a39f227c80cbf369767badc32cba2b225147d1 Patch