CVE-2026-68381: ksmbd: pin conn during async oplock break notification
In the Linux kernel, the following vulnerability has been resolved:
ksmbd: pin conn during async oplock break notification
smb2oplockbreaknoti() and smb2leasebreaknoti() store a ksmbdconn pointer in an async ksmbdwork and then queue that work on ksmbd-io. The work only increments conn->rcount, which prevents teardown from passing the pending-request wait after the increment, but it does not pin the struct ksmbdconn 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 ksmbdconnwrite() and ksmbdconnrcountdec().
Take a real conn reference when publishing the conn pointer to the async work item, and drop it after the notification work has decremented rcount. Apply the same lifetime rule to lease break notification, which uses the same work->conn pattern.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-68381?
The severity of CVE-2026-68381 is rated at 48.
How do I fix CVE-2026-68381?
To fix CVE-2026-68381, update to the latest version of the Linux kernel where the vulnerability has been resolved.
What systems are affected by CVE-2026-68381?
CVE-2026-68381 affects systems running affected versions of the Linux kernel that utilize the ksmbd component.
What type of vulnerability is CVE-2026-68381?
CVE-2026-68381 is an information leak vulnerability, specifically related to connection handling in ksmbd.
Is there a workaround for CVE-2026-68381?
Currently, the recommended approach is to apply the kernel update, as a specific workaround for CVE-2026-68381 has not been provided.