CVE-2026-64396
CVE CVE-2026-64396EUVD EUVD-2026-48940Published 2026-07-25T08:50:40.000ZLast changed 2026-08-05T12:41:34.000ZCVSS 8.8
What the advisory describes
In the Linux kernel, the following vulnerability has been resolved: ksmbd: fix UAF of struct file_lock in SMB2_LOCK deferred-lock cancellation When a blocking byte-range lock request is deferred in the FILE_LOCK_DEFERRED path, ksmbd registers the asynchronous work into the connection's async_requests list via setup_async_work(). The cancel callback smb2_remove_blocked_lock() holds a reference to the flock. If the lock waiter is subsequently woken up but the work state is no longer KSMBD_WORK_ACTIVE (e.g., due to a concurrent cancellation), the cleanup path calls locks_free_lock(flock) without dequeuing the work from the async_requests list. Concurrently, smb2_cancel() walks the list under conn->request_lock and invokes the cancel callback, which then dereferences the already freed 'flock'. This leads to a slab-use-after-free inside __wake_up_common. Fix this by restructuring the cleanup logic after the worker returns from ksmbd_vfs_posix_lock_wait(). Move list_del(&smb_lock->llist) and release_async_work(work) to the top of the cleanup block. This guarantees that the async work is completely dequeued and serialized under conn->request_lock before locks_free_lock(flock) is called, rendering the flock unreachable for any concurrent smb2_cancel().
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 e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 <367c42a611fe488b7b03f1f6737f4dee0e8b20a2; 5.15; e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 <7703fd9aba1f2483c8e55f9ff73b7663e0761ed9; e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 <463bbd79698513af4dad50fe1c573825f297ca2e; patch: 7.1.4; patch: 0; patch: 6.18.39; patch: 7.2-rc1; patch: 6.1.178; patch: 6.6.145; e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 <5c75275c0fc9a2deb0d8f5604edcb16f288171c8; e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 <5aa1cb01155f96824003baf7997cdf1f150caba3; e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 <d20d1c8ba5765d1d12eefc0aee6385ab3f240e1e; patch: 6.12.96
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.