# CVE-2026-99536: ksmbd: prevent session binding in compound requests

Status: published. Published: 2026-11-19. Updated: 2026-11-22.

In the Linux kernel, the following vulnerability has been resolved:

ksmbd: prevent session binding in compound requests

A failed multichannel binding can retain its target session on the work
item so that the error response can be signed. Subsequent compound
commands can then use that session together with a tree connection left
over from an earlier command.

Limit binding SESSION_SETUP requests to standalone messages during
message validation, before smb2_sess_setup() can replace work->sess.
Check both NextCommand and the current request offset to cover binding
in the first, middle and last positions of a compound. The existing
validation error path returns STATUS_INVALID_PARAMETER and stops
processing the remaining commands.

This intentionally limits support for compounded binding. It is not a
protocol requirement that binding be standalone. Standalone binding and
non-binding compounds retain their existing behavior, without changing
session, tree or response encryption handling.

## Remediation

No remediation reported in collected sources

## Affected products and versions

- Linux / Linux: ≥ 4b706360ffb7e459cb3d3edae30b06a584f6eddd; < 4f148586c9cb18ad47b5f41153139d0fefa596d3 (affected, git); ≥ 4b706360ffb7e459cb3d3edae30b06a584f6eddd; < 19f8fd6b5ced33b02a083759e6901f9d6e8076df (affected, git); a1f2ada2e4d33d316939dedefbfd2e7d94a0c61f (affected, git); ≥ 7.1.5; < 7.2 (affected, semver). Source: CNA: Linux
- Linux / Linux: 7.2 (affected); ≥ 0; < 7.2 (unaffected, semver); ≥ 7.3.2; ≤ 7.3.* (unaffected, semver); ≥ 7.4-rc1; ≤ * (unaffected, original_commit_for_fix). Source: CNA: Linux

## Severity and prioritization

- CVSS 3.1: 7.1 (high); CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:L; source: CNA: Linux

- CVSS 3.1: 7.1 (high); CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:L; source: NVD: 416baaa9-dc9f-4396-8d5f-8c081fb06d67

- CISA KEV: No listing in collected sources

- EPSS: 0.10% as of 2026-11-21; percentile 1.00%

- SSVC: Not available

- Weaknesses: Not reported

## Exploit evidence

No exploit evidence in collected sources. This is not proof of no exploitation.

## References

- https://git.kernel.org/stable/c/4f148586c9cb18ad47b5f41153139d0fefa596d3 (CNA: Linux)

- https://git.kernel.org/stable/c/19f8fd6b5ced33b02a083759e6901f9d6e8076df (CNA: Linux)

- https://git.kernel.org/stable/c/19f8fd6b5ced33b02a083759e6901f9d6e8076df (416baaa9-dc9f-4396-8d5f-8c081fb06d67)

- https://git.kernel.org/stable/c/4f148586c9cb18ad47b5f41153139d0fefa596d3 (416baaa9-dc9f-4396-8d5f-8c081fb06d67)

## Provenance

- CNA: Linux: https://www.cve.org/CVERecord?id=CVE-2026-99536; retrieved 2026-11-22; source updated 2026-11-22

- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-99536; retrieved 2026-11-22; source updated 2026-11-22

- FIRST EPSS: https://api.first.org/data/v1/epss?cve=CVE-2026-99536; retrieved 2026-11-22; source updated Not reported

Revision: 28ca9bc42b1e8509c9900b93293146fc7d6184c5bd5443b82fa80b9fab588036

Canonical: https://y2.dev/cve/CVE-2026-99536

## Agent and API access

Public CVE pages, Markdown, and JSON are free to read without an account or API key.

- Public catalog: https://y2.dev/cve/index.json. Follow nextCursor with the same search, filters, sort, and limit (1–100). A null cursor marks the end.

- WebMCP: search_cve_disclosures, get_cve_disclosure, get_cve_page_markdown, get_y2_cve_access. Available in compatible browsers.

- Cyber API: https://api.y2.dev/api/v2/cyber/cves and https://api.y2.dev/api/v2/cyber/cves/{cveId}.

- Y2 Pro or Elite: create a workspace API key with the intel:cyber scope and send Authorization: Bearer <Y2_API_KEY>. Setup: https://y2.dev/docs/api/create-key.

- x402: Pay per request without an account or API key. Omit Authorization, read the HTTP 402 PAYMENT-REQUIRED challenge, validate its current requirements, and retry with PAYMENT-SIGNATURE through an authorized payment client. These browser tools never make payments. Guide: https://y2.dev/docs/api/x402.

- OpenAPI: https://y2.dev/api/openapi.yaml. Agent access metadata: https://y2.dev/cve/agent.json.

Collected public records only. Check source status for coverage and freshness.