CVE-2026-68381ksmbd: pin conn during async oplock break notification
- 9.8CriticalCVSS base score
- 0.60%Exploitation in 30 daysEPSS · top 51% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
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.
Timeline
ID reserved
By Linux
- 11 days later
· 11 days later
Published
- 3 months later
· 3 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | Critical9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVDNVD · Received | 3.1 | Critical9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
- EPSS (exploitation in 30 days)
- 0.60% · top 51% of all CVEs (15 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: yes · Technical impact: total
The list uses the assigner's score when there is one, then CISA's, then NVD's: Critical 9.8.
Affected products
- affected 8e6508c7ecb1802909f294827eff38f301d0c937 – < dab1493bc9d97947f1219d6823c2e2a28636021b
- affected 09aeab68033161cb54f194da93e51a11aee6144b – < 0f72fc9659d7f585460d43c158055df5afdcffb6
- affected a4261bbc33fbf99b99c80aa3a2c5097611802980 – < 793e1c7041b93af96ff87e678329bc16aee7ba88
- affected 3aa660c059240e0c795217182cf7df32909dd917 – < 6ecb252efa0b413ac3d9979fb4eec247f8fc1258
- affected 3aa660c059240e0c795217182cf7df32909dd917 – < 14062c74e5b25c27edcff7a2fe0dc701c930b372
- affected 3aa660c059240e0c795217182cf7df32909dd917 – < aa5d8f3f96aa11a4a54ce993c11ce8af11c546f9
- affected f17d1c63a76b0fe8e9c78023a86507a3a6d62cfa
- affected 6.6.84 – < 6.6.148
- affected 6.12.20 – < 6.12.101
- affected 6.13.8 – < 6.14
- affected 6.14
- unaffected < 6.14
- unaffected 6.6.148 – ≤ 6.6.*
- unaffected 6.12.101 – ≤ 6.12.*
- unaffected 6.18.42 – ≤ 6.18.*
- unaffected 7.1.6 – ≤ 7.1.*
- unaffected 7.2 – ≤ *
References
References6
- https://git.kernel.org/stable/c/dab1493bc9d97947f1219d6823c2e2a28636021b (opens in a new tab)
- https://git.kernel.org/stable/c/0f72fc9659d7f585460d43c158055df5afdcffb6 (opens in a new tab)
- https://git.kernel.org/stable/c/793e1c7041b93af96ff87e678329bc16aee7ba88 (opens in a new tab)
- https://git.kernel.org/stable/c/6ecb252efa0b413ac3d9979fb4eec247f8fc1258 (opens in a new tab)
- https://git.kernel.org/stable/c/14062c74e5b25c27edcff7a2fe0dc701c930b372 (opens in a new tab)
- https://git.kernel.org/stable/c/aa5d8f3f96aa11a4a54ce993c11ce8af11c546f9 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-55567 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-68381)Record last updated .