CVE-2026-64016

CVE CVE-2026-64016EUVD EUVD-2026-45589Published 2026-07-19T15:39:11.000ZLast changed 2026-08-05T12:38:13.000ZCVSS 9.8

What the advisory describes

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.

Source: EUVD (ENISA), in the words of the advisory.

Products the advisory names

These come from the advisory itself, not from any check we performed.

• Linux — Linux 97a0cd55283b4e63fd92804da91c8d9896adcad9 <6cb0b9385320110fe24a5d5ac0000ade4bb3a3f3; 1baff47b81f94f9231c91236aa511420d0e266b9 <3515503322f4819277091839eed46b695096aca5; ce2e164c1c51c3f7813b80f8c926836e896bcbb3 <a1a39f227c80cbf369767badc32cba2b225147d1; 6.18.33 <6.18.34; 7.0.10 <7.0.11

The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.

Carried in the product catalogue

An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.

• Linux — Linux

Patchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.