Skip to content
Threat Brief

← All advisories

CVE-2026-99531

Severity unknownNo known exploitationFix available

ksmbd: verify transform SessionId matches the decrypted header

Record last updated

CVSS score

None

No score published yet

EPSS, chance of exploitation in 30 days

0.2%

Higher than 6% of scored CVEs. A prediction, not evidence.

CISA remediation deadline

None

Not in the KEV catalog

Description

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.

Patching and mitigation

Patch status
Fix available (source: CVE record (Linux))
Fix documented (source date)
Mitigation
None documented
Vendor guidance
No vendor link on record

Affected products

VendorProductAffected versionsFixed inPer
LinuxLinuxfrom e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 before 7f30b886c5a1a2b3d9342ea82d0699eff812a4727f30b886c5a1a2b3d9342ea82d0699eff812a472CVE Program
LinuxLinuxfrom e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 before 8c5f62dd9a0b61e0082d419796e0743e820bd0028c5f62dd9a0b61e0082d419796e0743e820bd002CVE Program
LinuxLinuxfrom e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 before 798214e6fafcdcc29f5ba2661a473232b5e70cfb798214e6fafcdcc29f5ba2661a473232b5e70cfbCVE Program
LinuxLinuxfrom e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 before b150049dffd0865fb6e60ce843299216687f02adb150049dffd0865fb6e60ce843299216687f02adCVE Program
LinuxLinux5.15Not documentedCVE Program
LinuxLinux (unaffected)from 6.12.117 up to and including 6.12.*Not documentedCVE Program
LinuxLinux (unaffected)from 6.18.61 up to and including 6.18.*Not documentedCVE Program
LinuxLinux (unaffected)from 7.3.2 up to and including 7.3.*Not documentedCVE Program
LinuxLinux (unaffected)7.4-rc1Not documentedCVE Program
LinuxLinux (unaffected)all versions before 5.15Not documentedCVE Program

Timeline

  1. Disclosure

    CVE record published by Linux

    Source: CVE Program (opens in a new tab)

  2. Patch

    Fix documented by CVE record (Linux)

    Source: CVE record (Linux) (opens in a new tab)

Vendor guidance and references