CVE-2026-90167: Linux kernel · ksmbd: serialize oplock close with pending break ownership
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in dc1e34f78dfab755fab9ad820ac5f82348fe1792 : update Linux kernel when convenient.
Data as of 26 Oct 2026, 17:30 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 10% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in dc1e34f78dfab755fab9ad820ac5f82348fe1792, b0148dc5625dbfd50596ac63c7487c12e8a8ab03, 7148a6c06ddf1c263a1cf422bee541f24d3d3926 +2
Exploitation evidence
Disclosed: evidence found.
CVE published 17 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
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.
References
- git.kernel.org/stable/c/7148a6c06ddf1c263a1cf422bee541f24d3d3926 (opens in a new tab)
- git.kernel.org/stable/c/7d6e682b7633120c2f93400b8c6f335d9d8e5318 (opens in a new tab)
- git.kernel.org/stable/c/dc1e34f78dfab755fab9ad820ac5f82348fe1792 (opens in a new tab)
- git.kernel.org/stable/c/5f97bac88bfb333f426f01c118b8235e75af8d96 (opens in a new tab)
- git.kernel.org/stable/c/b0148dc5625dbfd50596ac63c7487c12e8a8ab03 (opens in a new tab)