Back to CVE records
Medium 5.5Published Apr 24, 2026

CVE-2026-31610ksmbd: fix mechToken leak when SPNEGO decode fails after token alloc

Updated under an hour ago ()

Does this affect you?

It affects Linux and 1 other product. Add what you run to find out whether that includes you.

No exploitation reported and no EPSS estimate yet.

In the Linux kernel, the following vulnerability has been resolved: ksmbd: fix mechToken leak when SPNEGO decode fails after token alloc The kernel ASN.1 BER decoder calls action callbacks incrementally as it walks the input. When ksmbd_decode_negTokenInit() reaches the mechToken [2] OCTET STRING element, ksmbd_neg_token_alloc() allocates conn->mechToken immediately via kmemdup_nul(). If a later element in the same blob is malformed, then the decoder will return nonzero after the allocation is already live. This could happen if mechListMIC [3] overrunse the enclosing SEQUENCE. decode_negotiation_token() then sets conn->use_spnego = false because both the negTokenInit and negTokenTarg grammars failed. The cleanup at the bottom of smb2_sess_setup() is gated on use_spnego: if (conn->use_spnego && conn->mechToken) { kfree(conn->mechToken); conn->mechToken = NULL; } so the kfree is skipped, causing the mechToken to never be freed. This codepath is reachable pre-authentication, so untrusted clients can cause slow memory leaks on a server without even being properly authenticated. Fix this up by not checking check for use_spnego, as it's not required, so the memory will always be properly freed. At the same time, always free the memory in ksmbd_conn_free() incase some other failure path forgot to free it.

CVSS
5.5 MEDIUM (v3.1, NVD)CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Weakness (CWE)
Not given
Known exploited
Not in CISA's KEV catalog
EPSS (exploitation in the next 30 days)
Not loaded for this CVE
Assigned by
Linux
NVD analysis
Modified
Record last updated
Jul 24, 2026
First seen by InfoSec Signals
Oct 9, 2026

Affected products

Affected products
Linux Linux
linux:linux (from the name)
from fad4161b5cd01a24202234976ebbb133f7adc0b5 before ae9cdb29efed20ffdee9ff3b0bb72fb369c353da; from fad4161b5cd01a24202234976ebbb133f7adc0b5 before bd4a7fb04f06f419b0e93d8b52fe32067eb312d1; from fad4161b5cd01a24202234976ebbb133f7adc0b5 before 745a535461bbb90a56d9357573c9f97a5c12abe1; from fad4161b5cd01a24202234976ebbb133f7adc0b5 before dd577cb55588ec3fbc66af3621280306601c4192; from fad4161b5cd01a24202234976ebbb133f7adc0b5 before dd53414e301beb915fe672dc4c4a51bafb917604; from fad4161b5cd01a24202234976ebbb133f7adc0b5 before 269c800a7a7e363459291885b35f7bc72e231ed6; from fad4161b5cd01a24202234976ebbb133f7adc0b5 before 6c8c44e6553b9f072f62d9875e567766eb293162; from fad4161b5cd01a24202234976ebbb133f7adc0b5 before ad0057fb91218914d6c98268718ceb9d59b388e1
CNA record
linux linux_kernel
linux:linux_kernel
from 5.15 before 6.6.136; from 6.7 before 6.12.83; from 6.13 before 6.18.24; from 6.19 before 6.19.14; from 7.0 before 7.0.1
NVD

References

References

The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.

Your cookie choices
We use essential cookies to run this site, and, only with your consent, an advertising cookie from Google to measure whether our ads lead to sign-ups and subscriptions. See our for details.