{
  "schema_version": "1.6.1",
  "id": "RPI-CVE-2023-32249",
  "modified": "2026-10-09T11:39:44Z",
  "upstream": [
    "CVE-2023-32249"
  ],
  "published": "2025-08-16T13:26:03Z",
  "summary": "ksmbd: not allow guest user on multichannel",
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nksmbd: not allow guest user on multichannel\n\nThis patch return STATUS_NOT_SUPPORTED if binding session is guest.",
  "severity": [
    {
      "type": "CVSS_V3",
      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N"
    }
  ],
  "affected": [
    {
      "package": {
        "ecosystem": "Raspberry Pi OS:12",
        "name": "linux"
      },
      "versions": [
        "1:6.1.21-1+rpt1"
      ],
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "linux-image-6.1.0-rpi1-rpi-v6",
            "binary_version": "1:6.1.21-1+rpt1"
          },
          {
            "binary_name": "linux-image-6.1.0-rpi1-rpi-v7",
            "binary_version": "1:6.1.21-1+rpt1"
          },
          {
            "binary_name": "linux-image-6.1.0-rpi1-rpi-v7l",
            "binary_version": "1:6.1.21-1+rpt1"
          },
          {
            "binary_name": "linux-image-6.1.0-rpi1-rpi-v8",
            "binary_version": "1:6.1.21-1+rpt1"
          }
        ]
      },
      "database_specific": {
        "per_version": {
          "1:6.1.21-1+rpt1": {
            "linux_commit": "0afb5e98488aed7017b9bf321b575d0177feb7ed",
            "upstream_version": "6.1.21",
            "assessment": "commit ancestry (strak rule)",
            "upstream_fixed": "6.1.28"
          }
        }
      }
    }
  ],
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://www.cve.org/CVERecord?id=CVE-2023-32249"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/ed76d3a8910be06cd4e4ba63bf6075bf903945a1"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/1f0490586544455e5be698be2e6c30077b4ec461"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/4a98e859c4673013385a54084e0cd865695ca072"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/088131b7b01099720a528a72005ff17868705d40"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/3353ab2df5f68dab7da8d5ebb427a2d265a1f2b2"
    }
  ],
  "database_specific": {
    "source": "https://git.kernel.org/pub/scm/linux/security/vulns.git",
    "upstream_modified": "2026-08-15T12:24:41Z",
    "severity": {
      "source": "kernel CNA",
      "cvss_v3_score": 9.1,
      "cvss_v3_severity": "Critical",
      "scenario": "AV:N - The flaw is in ksmbd (fs/ksmbd/) SMB2 SESSION_SETUP multichannel binding, reached over TCP/445 from a remote peer with no local access required.\nAC:L - The attacker fully controls the binding connection and SESSION_SETUP messages; SessionIds are sequential ida allocations and the bind path needs no race or special memory layout, so the hijack is reliably triggerable once a live session exists.\nPR:N - ZDI-23-697 and the vulnerable ntlm_authenticate path show anonymous/guest reauthentication skips credential verification during binding, so no valid SMB credentials for the target session are required.\nUI:N - Exploitation requires only attacker-sent SMB negotiate/session-setup traffic against an already-active victim session; no additional victim action is needed.\nS:U - Impact stays within the ksmbd server\u2019s authority (hijacked SMB session and its share/file access) and does not cross a VM, kernel/user, or other security boundary.\nC:H - Successful binding attaches the attacker to an arbitrary live session via global session lookup, granting full read access to that user\u2019s connected shares and open files.\nI:H - The hijacked session retains the victim\u2019s authorization for tree connects and file operations, so the attacker can create, modify, or delete data with the victim\u2019s SMB privileges.\nA:N - This is an authentication/session-isolation bug, not memory corruption; it does not cause kernel oops/panic or otherwise deny availability of the component."
    }
  }
}