Skip to main content
VulnerabilityPublished Updated

CVE-2026-90167: Linux kernel · ksmbd: serialize oplock close with pending break ownership

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-90167· Medium

Not known to be exploited · fixed in dc1e34f78dfab755fab9ad820ac5f82348fe1792 : update Linux kernel when convenient.

Data as of 30 Oct 2026, 16:33 UTC

Severity
Medium

Rated by Threat Radar · CVSS not yet scored by NVD

Thin evidence

One scorer or none
Patch
Available – fixed in dc1e34f78dfab755fab9ad820ac5f82348fe1792, b0148dc5625dbfd50596ac63c7487c12e8a8ab03, 7148a6c06ddf1c263a1cf422bee541f24d3d3926 +3

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 17 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 30 Oct 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9, < dc1e34f78dfab755fab9ad820ac5f82348fe1792
Fixed in
  • dc1e34f78dfab755fab9ad820ac5f82348fe1792
LinuxLinuxAffected
  • ≥ e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9, < b0148dc5625dbfd50596ac63c7487c12e8a8ab03
Fixed in
  • b0148dc5625dbfd50596ac63c7487c12e8a8ab03
LinuxLinuxAffected
  • ≥ e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9, < 7148a6c06ddf1c263a1cf422bee541f24d3d3926
Fixed in
  • 7148a6c06ddf1c263a1cf422bee541f24d3d3926
LinuxLinuxAffected
  • ≥ e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9, < 7d6e682b7633120c2f93400b8c6f335d9d8e5318
Fixed in
  • 7d6e682b7633120c2f93400b8c6f335d9d8e5318
LinuxLinuxAffected
  • ≥ e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9, < 5f97bac88bfb333f426f01c118b8235e75af8d96
Fixed in
  • 5f97bac88bfb333f426f01c118b8235e75af8d96
LinuxLinuxAffected
  • ≥ e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9, < 02a31a30ccd09f3ff35ab5861c04209c381aa5dd
Fixed in
  • 02a31a30ccd09f3ff35ab5861c04209c381aa5dd

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

Community reviews

Loading reviews…