Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. · 46 days later

    Published

  3. · 3 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-31610, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.14% · top 97% of all CVEs (19 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected fad4161b5cd01a24202234976ebbb133f7adc0b5 – < ae9cdb29efed20ffdee9ff3b0bb72fb369c353da
    • affected fad4161b5cd01a24202234976ebbb133f7adc0b5 – < bd4a7fb04f06f419b0e93d8b52fe32067eb312d1
    • affected fad4161b5cd01a24202234976ebbb133f7adc0b5 – < 745a535461bbb90a56d9357573c9f97a5c12abe1
    • affected fad4161b5cd01a24202234976ebbb133f7adc0b5 – < dd577cb55588ec3fbc66af3621280306601c4192
    • affected fad4161b5cd01a24202234976ebbb133f7adc0b5 – < dd53414e301beb915fe672dc4c4a51bafb917604
    • affected fad4161b5cd01a24202234976ebbb133f7adc0b5 – < 269c800a7a7e363459291885b35f7bc72e231ed6
    • affected fad4161b5cd01a24202234976ebbb133f7adc0b5 – < 6c8c44e6553b9f072f62d9875e567766eb293162
    • affected fad4161b5cd01a24202234976ebbb133f7adc0b5 – < ad0057fb91218914d6c98268718ceb9d59b388e1
  • Linux · Linux

    • affected 5.15
    • unaffected < 5.15
    • unaffected 5.15.212 – ≤ 5.15.*
    • unaffected 6.1.178 – ≤ 6.1.*
    • unaffected 6.6.136 – ≤ 6.6.*
    • unaffected 6.12.83 – ≤ 6.12.*
    • unaffected 6.18.24 – ≤ 6.18.*
    • unaffected 6.19.14 – ≤ 6.19.*
    • unaffected 7.0.1 – ≤ 7.0.*
    • unaffected 7.1 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-31610 badge
[![CVE-2026-31610](https://cveledger.app/badge/CVE-2026-31610.svg)](https://cveledger.app/cve/CVE-2026-31610)

Record last updated .