CVE-2026-90167ksmbd: serialize oplock close with pending break ownership
- —Not scoredno CVSS score yet
- 0.21%Exploitation in 30 daysEPSS · top 88% 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: serialize oplock close with pending break ownership close may abort an in-flight oplock break while another breaker already holds an opinfo reference. Releasing pending_break wakes that waiter, but without serializing the close transition with bit acquisition it can become a new break owner through the test_and_set_bit() fast path. It can then overwrite OPLOCK_CLOSING with OPLOCK_ACK_WAIT and continue a break for a dying opinfo. Make OPLOCK_CLOSING terminal once the opinfo is removed from the inode list. Serialize that transition, pending_break acquisition, and OPLOCK_ACK_WAIT setup with an opinfo state lock. A breaker which loses the race releases its ownership and returns -ENOENT. Explicitly wake pending_break waiters during close so they can observe the terminal state. Also prevent ACK and timeout paths from replacing OPLOCK_CLOSING with OPLOCK_STATE_NONE.
Timeline
ID reserved
By Linux
- 6 days later
· 6 days later
Published
- 43 days later
· 43 days 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
No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.
- EPSS (exploitation in 30 days)
- 0.21% · top 88% of all CVEs (16 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 – < 02a31a30ccd09f3ff35ab5861c04209c381aa5dd
- affected e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 – < 7148a6c06ddf1c263a1cf422bee541f24d3d3926
- affected e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 – < 7d6e682b7633120c2f93400b8c6f335d9d8e5318
- affected e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 – < dc1e34f78dfab755fab9ad820ac5f82348fe1792
- affected e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 – < 5f97bac88bfb333f426f01c118b8235e75af8d96
- affected e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 – < b0148dc5625dbfd50596ac63c7487c12e8a8ab03
- affected 5.15
- unaffected < 5.15
- unaffected 6.1.191 – ≤ 6.1.*
- unaffected 6.6.160 – ≤ 6.6.*
- unaffected 6.12.114 – ≤ 6.12.*
- unaffected 6.18.57 – ≤ 6.18.*
- unaffected 7.2.6 – ≤ 7.2.*
- unaffected 7.3 – ≤ *
References
References6
- https://git.kernel.org/stable/c/02a31a30ccd09f3ff35ab5861c04209c381aa5dd (opens in a new tab)
- https://git.kernel.org/stable/c/7148a6c06ddf1c263a1cf422bee541f24d3d3926 (opens in a new tab)
- https://git.kernel.org/stable/c/7d6e682b7633120c2f93400b8c6f335d9d8e5318 (opens in a new tab)
- https://git.kernel.org/stable/c/dc1e34f78dfab755fab9ad820ac5f82348fe1792 (opens in a new tab)
- https://git.kernel.org/stable/c/5f97bac88bfb333f426f01c118b8235e75af8d96 (opens in a new tab)
- https://git.kernel.org/stable/c/b0148dc5625dbfd50596ac63c7487c12e8a8ab03 (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-81760 (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-90167)Record last updated .