CVE-2026-99531

published 19 Nov 2026 · updated 21 Nov 2026

ksmbd: verify transform SessionId matches the decrypted header

7.5HighCVSS 7.5EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel b150049dffd0865fb6e60ce843299216687f02ad, Kernel 798214e6fafcdcc29f5ba2661a473232b5e70cfb, Kernel 7f30b886c5a1a2b3d9342ea82d0699eff812a472 and 4 more.

In the Linux kernel, the following vulnerability has been resolved: ksmbd: verify transform SessionId matches the decrypted header When an encrypted request comes in, the decryption key is picked by the SessionId in the transform header, but the request is then authorized under whatever session the decrypted inner header names. Nothing ever compares the two, so on a connection with more than one session a client can get a request decrypted with one session's key and run it as another session. Encrypted requests are exempt from signing too, so a valid AEAD tag is the only proof of session identity, and it is checked against the wrong session. MS-SMB2 says the server must check that the transform SessionId matches the one in the decrypted SMB2 header and treat a mismatch as a protocol error. Add that check in __handle_ksmbd_work() after decryption, before dispatching: the message has to be at least one fixed SMB2 header, the first operation must not set SMB2_FLAGS_RELATED_OPERATIONS and its SessionId must match the transform SessionId, and every following non-related operation in a compound chain must carry the same SessionId. NextCommand offsets must be 8-byte aligned and stay inside the message; the bounds check is done by subtraction so it cannot wrap. When the decrypted payload is a compression transform, the existing decompression step runs first and the decompressed SMB2 message is checked instead, since a compression transform header carries no SessionId.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel>=e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 <b150049dffd0865fb6e60ce843299216687f02ad, >=e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 <798214e6fafcdcc29f5ba2661a473232b5e70cfb, >=e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 <7f30b886c5a1a2b3d9342ea82d0699eff812a472, >=e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 <8c5f62dd9a0b61e0082d419796e0743e820bd002, =5.15b150049dffd0865fb6e60ce843299216687f02ad, 798214e6fafcdcc29f5ba2661a473232b5e70cfb, 7f30b886c5a1a2b3d9342ea82d0699eff812a472, 8c5f62dd9a0b61e0082d419796e0743e820bd002
linux-kernel: Kernel>=6.13.0 <6.18.61, >=6.19.0 <7.3.2, >=5.15.0 <6.12.1176.18.61, 7.3.2, 6.12.117

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-99531 severity on Zeptric[![CVE-2026-99531](https://zeptric.io/badge/cve/CVE-2026-99531.svg)](https://zeptric.io/cve/CVE-2026-99531)