In the Linux kernel, the following vulnerability has been resolved: ksmbd: transport_ipc: validate payload size before reading handle… (CVE-2025-40084)
A vulnerability in the Linux kernel's ksmbd component was resolved by validating the payload size before reading a 4-byte handle. The function handle_response() previously dereferenced the payload as a 4 bytes without confirming the payload was at least that size, allowing a malformed or truncated message to cause an out-of-bounds read. The fix ensures the size is checked before dereferencing to prevent this issue.
AI Analysis
Technical Summary
The Linux kernel's ksmbd transport_ipc subsystem had a vulnerability (CVE-2025-40084) where handle_response() would read a 4-byte handle from the payload without verifying that the payload size was at least 4 bytes. This could lead to a 4-byte read beyond the declared payload size if a malformed or truncated message was received from ksmbd.mountd. The vulnerability was addressed by adding validation of the payload size before dereferencing the handle, mitigating the risk of out-of-bounds memory access.
Potential Impact
This vulnerability allows an attacker with local privileges and low complexity to cause a high impact on confidentiality and availability by reading memory beyond the intended payload boundary. The CVSS vector indicates no user interaction is required and privileges are low, making it a high-severity issue. However, no known exploits in the wild have been reported.
Mitigation Recommendations
A fix has been implemented in the Linux kernel to validate the payload size before reading the handle in ksmbd. Users should apply the official kernel updates that include this fix once available. Patch status is not yet confirmed — check the vendor advisory or Linux kernel mailing lists for current remediation guidance.
In the Linux kernel, the following vulnerability has been resolved: ksmbd: transport_ipc: validate payload size before reading handle… (CVE-2025-40084)
Description
A vulnerability in the Linux kernel's ksmbd component was resolved by validating the payload size before reading a 4-byte handle. The function handle_response() previously dereferenced the payload as a 4 bytes without confirming the payload was at least that size, allowing a malformed or truncated message to cause an out-of-bounds read. The fix ensures the size is checked before dereferencing to prevent this issue.
CVSS v3.1
Score 7.1high
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Linux kernel's ksmbd transport_ipc subsystem had a vulnerability (CVE-2025-40084) where handle_response() would read a 4-byte handle from the payload without verifying that the payload size was at least 4 bytes. This could lead to a 4-byte read beyond the declared payload size if a malformed or truncated message was received from ksmbd.mountd. The vulnerability was addressed by adding validation of the payload size before dereferencing the handle, mitigating the risk of out-of-bounds memory access.
Potential Impact
This vulnerability allows an attacker with local privileges and low complexity to cause a high impact on confidentiality and availability by reading memory beyond the intended payload boundary. The CVSS vector indicates no user interaction is required and privileges are low, making it a high-severity issue. However, no known exploits in the wild have been reported.
Mitigation Recommendations
A fix has been implemented in the Linux kernel to validate the payload size before reading the handle in ksmbd. Users should apply the official kernel updates that include this fix once available. Patch status is not yet confirmed — check the vendor advisory or Linux kernel mailing lists for current remediation guidance.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-pxm9-5xjv-gw34
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2025-40084"]
- Database Specific Severity
- HIGH
- Cvss Version
- 3.1
Threat ID: 6a6b72d69c2644c7f847aed0
Added to database: 07/30/2026, 15:50:46 UTC
Last enriched: 07/30/2026, 16:25:08 UTC
Last updated: 09/10/2026, 19:38:44 UTC
Views: 11
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.