CVE-2026-31610: ksmbd: fix mechToken leak when SPNEGO decode fails after token alloc
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.13% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 269c800a7a7e363459291885b35f7bc72e231ed6, 6c8c44e6553b9f072f62d9875e567766eb293162, 745a535461bbb90a56d9357573c9f97a5c12abe1; azl3 kernel 6.6.134.1-2 on Azure Linux 3.0 6.6.137.1-1; cbl2 kernel 5.15.202.1-1 on CBL-Mariner 2.0 Release Notes.
Low priority for now. Upgrade to Linux Linux 269c800a7a7e363459291885b35f7bc72e231ed6, 6c8c44e6553b9f072f62d9875e567766eb293162, 745a535461bbb90a56d9357573c9f97a5c12abe1; azl3 kernel 6.6.134.1-2 on Azure Linux 3.0 6.6.137.1-1; cbl2 kernel 5.15.202.1-1 on CBL-Mariner 2.0 Release Notes or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Apr 24, 2026
- Updated
- Nov 11, 2026
- EPSS
- 0.1% · 3th percentile
- CWE
- CWE-401
Report tools
Action score
22
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 5.15affected
- fad4161b5cd01a24202234976ebbb133f7adc0b5 and later · before ae9cdb29efed20ffdee9ff3b0bb72fb369c353daaffected · git
- fad4161b5cd01a24202234976ebbb133f7adc0b5 and later · before bd4a7fb04f06f419b0e93d8b52fe32067eb312d1affected · git
- fad4161b5cd01a24202234976ebbb133f7adc0b5 and later · before 745a535461bbb90a56d9357573c9f97a5c12abe1affected · git
- fad4161b5cd01a24202234976ebbb133f7adc0b5 and later · before dd577cb55588ec3fbc66af3621280306601c4192affected · git
- fad4161b5cd01a24202234976ebbb133f7adc0b5 and later · before dd53414e301beb915fe672dc4c4a51bafb917604affected · git
- fad4161b5cd01a24202234976ebbb133f7adc0b5 and later · before 269c800a7a7e363459291885b35f7bc72e231ed6affected · git
- fad4161b5cd01a24202234976ebbb133f7adc0b5 and later · before 6c8c44e6553b9f072f62d9875e567766eb293162affected · git
- fad4161b5cd01a24202234976ebbb133f7adc0b5 and later · before ad0057fb91218914d6c98268718ceb9d59b388e1affected · git
- before 5.15not affected · semver
Affected versions · NVD (5)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel5.15 and later · before 6.6.136
- linux linux kernel6.7 and later · before 6.12.83
- linux linux kernel6.13 and later · before 6.18.24
- linux linux kernel6.19 and later · before 6.19.14
- linux linux kernel7.0 and later · before 7.0.1
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.180-1 | 6.1.180-1 |
| Debian:13 | linux | before 6.12.85-1 | 6.12.85-1 |
| Debian:14 | linux | before 6.19.14-1 | 6.19.14-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2026-31608Apr 24, 2026 · smb: server: avoid double-free in smb_direct_free_sendmsg after smb_direct_flush_send_list()39Monitor
- ← EarlierCVE-2026-31609Apr 24, 2026 · smb: client: avoid double-free in smbd_free_send_io() after smbd_send_batch_flush()39Monitor
- Later →CVE-2026-31611Apr 24, 2026 · ksmbd: require 3 sub-authorities before reading sub_auth[2]34Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 269c800a7a7e363459291885b35f7bc72e231ed6 | Vendor (CNA) |
| Linux Linux | 6c8c44e6553b9f072f62d9875e567766eb293162 | Vendor (CNA) |
| Linux Linux | 745a535461bbb90a56d9357573c9f97a5c12abe1 | Vendor (CNA) |
| Linux Linux | ad0057fb91218914d6c98268718ceb9d59b388e1 | Vendor (CNA) |
| Linux Linux | ae9cdb29efed20ffdee9ff3b0bb72fb369c353da | Vendor (CNA) |
| Linux Linux | bd4a7fb04f06f419b0e93d8b52fe32067eb312d1 | Vendor (CNA) |
| Linux Linux | dd53414e301beb915fe672dc4c4a51bafb917604 | Vendor (CNA) |
| Linux Linux | dd577cb55588ec3fbc66af3621280306601c4192 | Vendor (CNA) |
| azl3 kernel 6.6.134.1-2 on Azure Linux 3.0 | 6.6.137.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 kernel 5.15.202.1-1 on CBL-Mariner 2.0 | Release Notes | Microsoft (MSRC) |
| debian:linux | 6.1.180-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-401 · Missing Release of Memory after Effective LifetimeCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/6c8c44e6553b9f072f62d9875e567766eb293162
- git.kernel.org/stable/c/745a535461bbb90a56d9357573c9f97a5c12abe1
- git.kernel.org/stable/c/ad0057fb91218914d6c98268718ceb9d59b388e1
- git.kernel.org/stable/c/ae9cdb29efed20ffdee9ff3b0bb72fb369c353da
- git.kernel.org/stable/c/bd4a7fb04f06f419b0e93d8b52fe32067eb312d1
- git.kernel.org/stable/c/dd53414e301beb915fe672dc4c4a51bafb917604
- git.kernel.org/stable/c/dd577cb55588ec3fbc66af3621280306601c4192
Vendor advisories and official records. Exploit/PoC links are deliberately left out.