CVE-2026-68381: ksmbd: pin conn during async oplock break notification

Published Aug 10, 2026
·
Updated

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

1 affected component
Linux Kernel

Event History

Aug 10, 2026
CVE Published
via MITRE·12:03 PM
Data Sourced
via MITRE·12:03 PM
Description
Data Sourced
via NVD·01:20 PM
Description
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-68381?

The severity of CVE-2026-68381 is rated at 48.

2

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.

3

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.

4

What type of vulnerability is CVE-2026-68381?

CVE-2026-68381 is an information leak vulnerability, specifically related to connection handling in ksmbd.

5

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.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203