CVE-2025-40084: ksmbd: transport_ipc: validate payload size before reading handle
In the Linux kernel, the following vulnerability has been resolved:
ksmbd: transport_ipc: validate payload size before reading handle
handle_response() dereferences the payload as a 4-byte handle without
verifying that the declared payload size is at least 4 bytes. A malformed
or truncated message from ksmbd.mountd can lead to a 4-byte read past the
declared payload size. Validate the size before dereferencing.
This is a minimal fix to guard the initial handle read.
Security readout for executives and security teams
Plain-English summary
A Linux ksmbd component can read four bytes beyond a message’s declared boundary when ksmbd.mountd supplies malformed or truncated data. This may expose kernel memory or crash the system. The CVSS rating is 7.1, but exploitation requires local, low-privileged access; the supplied sources do not establish a remote attack path.
Executive priority
Prioritize patching ksmbd-enabled file servers and multi-user systems where untrusted local access exists. Internet exposure alone does not establish exploitability from the supplied evidence. Systems without active ksmbd are lower priority, but teams should verify that condition rather than assume it.
Technical view
handle_response() in ksmbd transport IPC treated the payload as a four-byte handle without first confirming sufficient payload length. The correction validates the size before dereferencing. The stated impacts are high confidentiality loss and high availability loss, with no integrity impact. The bundle does not document whether the out-of-bounds read is reliably controllable.
Likely exposure
Exposure is most likely on systems running affected Linux kernels with ksmbd and its userspace ksmbd.mountd service active. The supplied affected-version data includes 5.15, 6.1.158, 6.6.115, 6.12.56, 6.17.6, and 6.18, but its structure is ambiguous; confirm status through the system’s kernel distributor.
Exploitation context
The CVSS vector describes a local, low-complexity attack requiring low privileges and no user interaction. The bundle marks this CVE as absent from KEV and provides no evidence of active exploitation, a public exploit, or remote reachability. Successful abuse could potentially disclose data or disrupt availability.
Researcher notes
The supplied version metadata is not a clean range and includes unusual entries, so exact branch boundaries cannot be established confidently. Five stable-kernel commits are cited as fixes. Further assessment should compare distributor source packages against those changes and examine whether untrusted local actors can influence the ksmbd.mountd IPC response path.
Mitigation direction
Update to a vendor-supported kernel containing the applicable cited stable fix.
Check Linux distributor advisories for exact fixed package versions and backports.
Disable ksmbd where SMB file serving is unnecessary, subject to operational approval.
Restrict local access and privileges on systems that must continue running ksmbd.
Validation and detection
Inventory kernel versions and determine whether the ksmbd module is present or loaded.
Confirm whether ksmbd.mountd and SMB file-serving functionality are active.
Verify the installed kernel package includes the relevant upstream fix or distributor backport.
Review kernel logs for ksmbd faults or unexplained crashes, without treating absence as proof of safety.
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-2025-40084 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
6Source 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.