CVE-2026-68381
CVE CVE-2026-68381EUVD EUVD-2026-55567Published 2026-08-10T12:03:59.000Z
What the advisory describes
In the Linux kernel, the following vulnerability has been resolved: ksmbd: pin conn during async oplock break notification smb2_oplock_break_noti() and smb2_lease_break_noti() store a ksmbd_conn pointer in an async ksmbd_work and then queue that work on ksmbd-io. The work only increments conn->r_count, which prevents teardown from passing the pending-request wait after the increment, but it does not pin the struct ksmbd_conn object. If connection teardown races with an oplock break notification, the last conn reference can be dropped before the queued worker finishes. The worker then uses the freed conn in ksmbd_conn_write() and ksmbd_conn_r_count_dec(). Take a real conn reference when publishing the conn pointer to the async work item, and drop it after the notification work has decremented r_count. Apply the same lifetime rule to lease break notification, which uses the same work->conn pattern.
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 6.12.20 <6.12.101; 3aa660c059240e0c795217182cf7df32909dd917 <6ecb252efa0b413ac3d9979fb4eec247f8fc1258; 6.14; patch: 7.1.6; patch: 6.6.148; a4261bbc33fbf99b99c80aa3a2c5097611802980 <793e1c7041b93af96ff87e678329bc16aee7ba88; patch: 0; f17d1c63a76b0fe8e9c78023a86507a3a6d62cfa; 6.13.8 <6.14; 3aa660c059240e0c795217182cf7df32909dd917 <aa5d8f3f96aa11a4a54ce993c11ce8af11c546f9; patch: 6.12.101; patch: 7.2-rc4; 09aeab68033161cb54f194da93e51a11aee6144b <0f72fc9659d7f585460d43c158055df5afdcffb6; 3aa660c059240e0c795217182cf7df32909dd917 <14062c74e5b25c27edcff7a2fe0dc701c930b372; 6.6.84 <6.6.148; patch: 6.18.42
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.