Skip to main content
VulnerabilityPublished

CVE-2026-99322: Linux kernel · ksmbd: rebind completed CREATE replays without draining the old channel

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-99322

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

Data as of 19 Nov 2026, 16:20 UTC

Severity
Unrated

Rated by Threat Radar · CVSS not yet scored by NVD

Thin evidence

One scorer or none
Patch
Available – fixed in 864bbcd5dc5e70d639a3011eae81a872b69ff402, 7b54fe3db87bc3dee16c66b400206978e515a705, 7.3

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Nov 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 18 Nov 2026.

What to do

Upgrade Linux kernel to 864bbcd5dc5e70d639a3011eae81a872b69ff402, 7b54fe3db87bc3dee16c66b400206978e515a705 or 7.3.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • >=7.2.6 <7.3
Fixed in
  • 864bbcd5dc5e70d639a3011eae81a872b69ff402
  • 7b54fe3db87bc3dee16c66b400206978e515a705
  • 7.3
LinuxLinuxAffected
  • =7.3
Fixed in–

Description

In the Linux kernel, the following vulnerability has been resolved: ksmbd: rebind completed CREATE replays without draining the old channel A completed DurableHandleReqV2 CREATE can be replayed through another channel while its original channel is exiting. The existing replay path returns the open but leaves its connection and oplock references pointing at the old channel. Its open count also stays on that channel, and a later CLOSE through the surviving channel decrements the wrong counter. After checking the owner, lease key and persistent flag, verify that an active open is still published in the requesting session's file table. Do this even when no oplock was granted, and before processing a consumed replay. Do not read a borrowed opinfo session pointer for this check. Keep a healthy original binding. If the original channel is exiting or releasing, move the open and its own oplock references to the requesting channel. Serialize this with CLOSE using the session file-table lock, and with detach, reconnect and notification snapshots using m_lock. The earlier lock index and lease-table changes make their lifetimes independent of this connection change. No old-channel r_count wait is needed, including when an unrelated request remains active there. Account final close against fp->conn in one place, balance durable detach and reconnect, and transfer the count with a replay binding change. A final global lookup put may run after CLOSE has removed the volatile id; unlink the open from the inode list on that final close as well. A live completed CREATE replay may follow a break that lowered the durable open's batch oplock. Apply the batch eligibility check only to detached reconnects, while retaining the owner, lease key and persistent flag checks for active replays.

References

Community reviews

Loading reviews…