{
  "affected": [
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:12",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "6.1.180-1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:13",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "6.12.85-1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:14",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "6.19.14-1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "details": "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-\u003emechToken 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-\u003euse_spnego = false because both the negTokenInit and negTokenTarg grammars failed.  The cleanup at the bottom of smb2_sess_setup() is gated on use_spnego:  \tif (conn-\u003euse_spnego \u0026\u0026 conn-\u003emechToken) { \t\tkfree(conn-\u003emechToken); \t\tconn-\u003emechToken = NULL; \t}  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.",
  "id": "DEBIAN-CVE-2026-31610",
  "modified": "2026-09-14T16:47:50.100576257Z",
  "published": "2026-04-24T15:16:40.257Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://security-tracker.debian.org/tracker/CVE-2026-31610"
    }
  ],
  "severity": [
    {
      "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
      "type": "CVSS_V3"
    }
  ],
  "upstream": [
    "CVE-2026-31610"
  ]
}