CVE-2023-3866: ksmbd: validate session id and tree id in the compound request
In the Linux kernel, the following vulnerability has been resolved:
ksmbd: validate session id and tree id in the compound request
This patch validate session id and tree id in compound request.
If first operation in the compound is SMB2 ECHO request, ksmbd bypass
session and tree validation. So work->sess and work->tcon could be NULL.
If secound request in the compound access work->sess or tcon, It cause
NULL pointer dereferecing error.
Security readout for executives and security teams
Plain-English summary
A remote, unauthenticated client can send a malformed compound SMB request to Linux ksmbd and trigger a NULL-pointer error. The expected impact is denial of service, potentially disrupting the host or file-sharing workload. The supplied CVSS score is 7.5; no confidentiality or integrity impact is identified.
Executive priority
Prioritize reachable production systems using ksmbd, especially internet-facing file servers or hosts where a kernel outage would interrupt critical operations. Remediation should be prompt but evidence does not support emergency incident declarations absent local indicators. Systems not using ksmbd are unlikely to be exposed.
Technical view
ksmbd failed to validate session and tree identifiers consistently across a compound SMB request. A leading SMB2 ECHO could bypass validation, leaving session or tree connection pointers NULL; a later operation could dereference them. The vector is network-accessible, low-complexity, unauthenticated, and requires no user interaction.
Likely exposure
Exposure is limited to systems using ksmbd where SMB is reachable by an attacker. The bundle lists Linux 5.15, 5.15.121, 6.1.36, 6.3.10, and 6.4, but its version structure is ambiguous. Confirm affected and fixed status using distribution guidance and backport records.
Exploitation context
The supplied record does not identify known active exploitation, and it is not marked as CISA KEV. The CVSS vector indicates remote, unauthenticated reachability and low attack complexity. Treat internet-exposed or broadly reachable ksmbd services as higher priority, without assuming exploitation has occurred.
Researcher notes
The failure is a missing validation issue resulting in NULL-pointer dereference and availability impact. The supplied affected-version array does not clearly distinguish introduced, affected, and fixed boundaries. Validate lineage using the four stable-kernel commits and distribution backports. No CWE or public exploitation evidence is supplied.
Mitigation direction
Apply a vendor-supported kernel update containing the referenced ksmbd validation fix.
Check distribution advisories because vendors may backport fixes without changing the upstream version as expected.
Restrict SMB access to trusted networks while affected systems remain unpatched.
Disable ksmbd where it is unnecessary, following vendor operational guidance.
Validation and detection
Inventory hosts loading or configuring ksmbd and identify their exact kernel package builds.
Determine whether SMB endpoints are reachable from untrusted or internet-facing networks.
Compare installed packages with distribution advisories and documented backport status.
After updating, confirm the running kernel is the remediated build.
Review kernel logs and availability alerts for unexplained ksmbd-related NULL-pointer failures.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2023-3866 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
0ADP providers
5Source links
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.