{"id":"CVE-2026-99322","state":"PUBLISHED","title":"ksmbd: rebind completed CREATE replays without draining the old channel","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nksmbd: rebind completed CREATE replays without draining the old channel\n\nA completed DurableHandleReqV2 CREATE can be replayed through another\nchannel while its original channel is exiting. The existing replay path\nreturns the open but leaves its connection and oplock references pointing\nat the old channel. Its open count also stays on that channel, and a\nlater CLOSE through the surviving channel decrements the wrong counter.\n\nAfter checking the owner, lease key and persistent flag, verify that an\nactive open is still published in the requesting session's file table.\nDo this even when no oplock was granted, and before processing a consumed\nreplay. Do not read a borrowed opinfo session pointer for this check.\n\nKeep a healthy original binding. If the original channel is exiting or\nreleasing, move the open and its own oplock references to the requesting\nchannel. Serialize this with CLOSE using the session file-table lock,\nand with detach, reconnect and notification snapshots using m_lock.\nThe earlier lock index and lease-table changes make their lifetimes\nindependent of this connection change. No old-channel r_count wait is\nneeded, including when an unrelated request remains active there.\n\nAccount final close against fp->conn in one place, balance durable detach\nand reconnect, and transfer the count with a replay binding change. A\nfinal global lookup put may run after CLOSE has removed the volatile id;\nunlink the open from the inode list on that final close as well.\n\nA live completed CREATE replay may follow a break that lowered the\ndurable open's batch oplock. Apply the batch eligibility check only to\ndetached reconnects, while retaining the owner, lease key and persistent\nflag checks for active replays.","publishedAt":"2026-11-19T14:21:30.827Z","updatedAt":"2026-11-22T11:07:41.563Z","severity":{"score":8.8,"label":"High","version":"3.1","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","source":"Linux"},"assigner":"Linux","products":["Linux Linux"],"affected":[{"vendor":"Linux","product":"Linux","defaultStatus":"unaffected","versions":[{"version":"bb8bf7eb13b518b379356a0c5dee8a23d6ee37ac","status":"affected","lessThan":"7b54fe3db87bc3dee16c66b400206978e515a705","versionType":"git"},{"version":"bb8bf7eb13b518b379356a0c5dee8a23d6ee37ac","status":"affected","lessThan":"864bbcd5dc5e70d639a3011eae81a872b69ff402","versionType":"git"},{"version":"c2b867861a48f0438afa6ce01f75e414df5431ad","status":"affected","versionType":"git"},{"version":"7.2.6","status":"affected","lessThan":"7.3","versionType":"semver"}],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","programFiles":["fs/smb/server/smb2pdu.c","fs/smb/server/vfs_cache.c","fs/smb/server/vfs_cache.h"]},{"vendor":"Linux","product":"Linux","defaultStatus":"affected","versions":[{"version":"7.3","status":"affected"},{"version":"0","status":"unaffected","lessThan":"7.3","versionType":"semver"},{"version":"7.3.2","status":"unaffected","lessThanOrEqual":"7.3.*","versionType":"semver"},{"version":"7.4-rc1","status":"unaffected","lessThanOrEqual":"*","versionType":"original_commit_for_fix"}],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","programFiles":["fs/smb/server/smb2pdu.c","fs/smb/server/vfs_cache.c","fs/smb/server/vfs_cache.h"]}],"references":["https://git.kernel.org/stable/c/7b54fe3db87bc3dee16c66b400206978e515a705","https://git.kernel.org/stable/c/864bbcd5dc5e70d639a3011eae81a872b69ff402"],"weaknesses":[],"ingestedAt":"2026-11-22T11:18:06.032Z","source":{"repository":"CVEProject/cvelistV5","path":"cves/2026/99xxx/CVE-2026-99322.json","commit":"247cc9beefd85903834df0592e88a44f4d599223","baselineCommit":"556c9d3a8cd17e218bb8e452ba7cd619a384ff47"},"raw":{"dataType":"CVE_RECORD","dataVersion":"5.2","cveMetadata":{"cveId":"CVE-2026-99322","state":"PUBLISHED","datePublished":"2026-11-19T14:21:30.827Z","dateUpdated":"2026-11-22T11:07:41.563Z","assignerShortName":"Linux","assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","dateReserved":"2026-09-25T10:25:14.408Z"},"containers":{"cna":{"title":"ksmbd: rebind completed CREATE replays without draining the old channel","descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\nksmbd: rebind completed CREATE replays without draining the old channel\n\nA completed DurableHandleReqV2 CREATE can be replayed through another\nchannel while its original channel is exiting. The existing replay path\nreturns the open but leaves its connection and oplock references pointing\nat the old channel. Its open count also stays on that channel, and a\nlater CLOSE through the surviving channel decrements the wrong counter.\n\nAfter checking the owner, lease key and persistent flag, verify that an\nactive open is still published in the requesting session's file table.\nDo this even when no oplock was granted, and before processing a consumed\nreplay. Do not read a borrowed opinfo session pointer for this check.\n\nKeep a healthy original binding. If the original channel is exiting or\nreleasing, move the open and its own oplock references to the requesting\nchannel. Serialize this with CLOSE using the session file-table lock,\nand with detach, reconnect and notification snapshots using m_lock.\nThe earlier lock index and lease-table changes make their lifetimes\nindependent of this connection change. No old-channel r_count wait is\nneeded, including when an unrelated request remains active there.\n\nAccount final close against fp->conn in one place, balance durable detach\nand reconnect, and transfer the count with a replay binding change. A\nfinal global lookup put may run after CLOSE has removed the volatile id;\nunlink the open from the inode list on that final close as well.\n\nA live completed CREATE replay may follow a break that lowered the\ndurable open's batch oplock. Apply the batch eligibility check only to\ndetached reconnects, while retaining the owner, lease key and persistent\nflag checks for active replays."}],"affected":[{"vendor":"Linux","product":"Linux","defaultStatus":"unaffected","versions":[{"version":"bb8bf7eb13b518b379356a0c5dee8a23d6ee37ac","status":"affected","lessThan":"7b54fe3db87bc3dee16c66b400206978e515a705","versionType":"git"},{"version":"bb8bf7eb13b518b379356a0c5dee8a23d6ee37ac","status":"affected","lessThan":"864bbcd5dc5e70d639a3011eae81a872b69ff402","versionType":"git"},{"version":"c2b867861a48f0438afa6ce01f75e414df5431ad","status":"affected","versionType":"git"},{"version":"7.2.6","status":"affected","lessThan":"7.3","versionType":"semver"}],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","programFiles":["fs/smb/server/smb2pdu.c","fs/smb/server/vfs_cache.c","fs/smb/server/vfs_cache.h"]},{"vendor":"Linux","product":"Linux","defaultStatus":"affected","versions":[{"version":"7.3","status":"affected"},{"version":"0","status":"unaffected","lessThan":"7.3","versionType":"semver"},{"version":"7.3.2","status":"unaffected","lessThanOrEqual":"7.3.*","versionType":"semver"},{"version":"7.4-rc1","status":"unaffected","lessThanOrEqual":"*","versionType":"original_commit_for_fix"}],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","programFiles":["fs/smb/server/smb2pdu.c","fs/smb/server/vfs_cache.c","fs/smb/server/vfs_cache.h"]}],"references":[{"url":"https://git.kernel.org/stable/c/7b54fe3db87bc3dee16c66b400206978e515a705"},{"url":"https://git.kernel.org/stable/c/864bbcd5dc5e70d639a3011eae81a872b69ff402"}],"metrics":[{"cvssV3_1":{"version":"3.1","vectorString":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","baseScore":8.8,"baseSeverity":"HIGH"},"scenarios":[{"lang":"en","value":"AV:N - The triggering bytes are an SMB2 CREATE on TCP/445 with SMB2_FLAGS_REPLAY_OPERATION and a DH2Q DurableHandleReqV2 CreateGuid. ksmbd_conn_handler_loop() queues that PDU to smb2_open(), which calls parse_durable_handle_context() and smb2_check_durable_replay().\nAC:L - The attacker completes the CREATE on one SMB3 channel, closes that socket so the conn is ksmbd_conn_releasing() while fp->conn remains set, and sends the replay on another channel. The opinfo->sess race is that same attacker's logoff or previous-session destroy running beside the replay.\nPR:L - smb2_check_user_session() rejects SMB2 CREATE without an SMB2_SESSION_VALID session, and smb2_check_durable_replay() then requires ksmbd_vfs_compare_durable_owner() to match the user that created the handle. Negotiate and session setup never reach this path.\nUI:N - The attacker performs session setup, the original CREATE, the channel close, and the replay CREATE. No other user has to open the file or change the server configuration.\nS:U - The bad replay and the opinfo->sess use-after-free stay inside ksmbd in the host kernel. They do not cross a guest-to-host, IOMMU, or other security boundary.\nC:H - smb2_check_durable_replay() reads opinfo->sess->id with no reference. alloc_opinfo() stores that raw pointer, session_fd_check() clears it, and ksmbd_session_destroy() kfree_sensitive()s the session, so reclaiming the slab discloses its contents.\nI:H - The same use-after-free lets the attacker place a controlled object in the freed ksmbd_session slot before smb2_check_durable_replay() uses opinfo->sess, giving a write into memory the kernel still treats as a live session.\nA:H - If that session slab is reused or unmapped before opinfo->sess->id is read, smb2_check_durable_replay() dereferences freed memory and oopses. The replay still returns the open while fp->conn and its oplock keep pointing at the channel ksmbd_conn_free() is tearing down."}]}],"providerMetadata":{"shortName":"Linux","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","dateUpdated":"2026-11-22T11:07:41.563Z"},"cpeApplicability":[{"nodes":[{"operator":"OR","negate":false,"cpeMatch":[{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"7.3","versionEndExcluding":"7.3.2"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"7.3","versionEndExcluding":"7.4-rc1"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"7.2.6"}]}]}],"x_generator":{"engine":"bippy-1.2.0"}}}}}