CVE-2026-64390
CVE CVE-2026-64390EUVD EUVD-2026-48934Published 2026-07-25T08:50:37.000ZLast changed 2026-08-05T12:41:27.000ZCVSS 8.8
What the advisory describes
In the Linux kernel, the following vulnerability has been resolved: ksmbd: track the connection owning a byte-range lock SMB2_LOCK adds each granted byte-range lock to both the file lock list and the lock list of the connection which handled the request. The final close and durable handle paths, however, remove the connection list entry while holding fp->conn->llist_lock. With SMB3 multichannel, the connection handling the LOCK request can be different from the connection which opened the file. The entry can therefore be removed under a different spinlock from the one protecting the list it belongs to. A concurrent traversal can then access freed struct ksmbd_lock and struct file_lock objects. Record the connection owning each lock's clist entry and hold a reference to it while the entry is linked. Use that connection and its llist_lock for unlock, rollback, close, and durable preserve. Durable reconnect assigns the new connection as the owner when publishing the locks again.
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 patch: 5.15.212; patch: 6.1.178; f5a544e3bab78142207e0242d22442db85ba1eff <427faaa52b0b399940c1a88065a5c310d10dad15; f5a544e3bab78142207e0242d22442db85ba1eff <22d38cf75b556c20b039743bdf3654d535b858be; patch: 7.1.4; patch: 6.12.97; 5.15; f5a544e3bab78142207e0242d22442db85ba1eff <c1016dd1d8b2bcd1158bbaabe94a31bb7e7431fb; patch: 0; patch: 6.6.145; f5a544e3bab78142207e0242d22442db85ba1eff <fe20d492a69a6f79e637f438072b212e21ed3b78; f5a544e3bab78142207e0242d22442db85ba1eff <66eb3643164e5e1029907793926c132f8b5c6148; f5a544e3bab78142207e0242d22442db85ba1eff <ea5c9bf99f626a15cc59f645dc895f2b3f01992e; patch: 6.18.40; patch: 7.2-rc1; f5a544e3bab78142207e0242d22442db85ba1eff <5fecc15a30cb9ebd310f7b52c1ab607edcea78f6
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
Does this concern one of your customers?
This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.
Try it for 28 daysPatchlage 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.