CVE-2026-99322

Source
https://cve.org/CVERecord?id=CVE-2026-99322
Import Source
https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-99322.json
JSON Data
https://api.osv.dev/v1/vulns/CVE-2026-99322
Downstream
Published
2026-11-19T14:21:30Z
Modified
2026-11-19T17:01:00Z
Summary
ksmbd: rebind completed CREATE replays without draining the old channel
Details

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.

Database specific
{
    "cna_assigner": "Linux",
    "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/99xxx/CVE-2026-99322.json"
}
References

Affected packages

Git / git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git

Affected ranges

Type
GIT
Repo
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Events
Introduced
bb8bf7eb13b518b379356a0c5dee8a23d6ee37ac
Fixed
7b54fe3db87bc3dee16c66b400206978e515a705
Fixed
864bbcd5dc5e70d639a3011eae81a872b69ff402
Type
GIT
Repo
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Events
Introduced
c2b867861a48f0438afa6ce01f75e414df5431ad

Affected versions

v7.*
v7.2.10
v7.2.11
v7.2.12
v7.2.13
v7.2.14
v7.2.15
v7.2.6
v7.2.7
v7.2.8
v7.2.9

Database specific

source
"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-99322.json"

Linux / Kernel

Package

Name
Kernel

Affected ranges

Type
ECOSYSTEM
Events
Introduced
7.2.6
Fixed
7.3
Type
ECOSYSTEM
Events
Introduced
7.3.0
Fixed
7.3.2

Database specific

source
"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-99322.json"