CVE-2024-26952: ksmbd: fix potencial out-of-bounds when buffer offset is invalid
In the Linux kernel, the following vulnerability has been resolved:
ksmbd: fix potencial out-of-bounds when buffer offset is invalid
I found potencial out-of-bounds when buffer offset fields of a few requests
is invalid. This patch set the minimum value of buffer offset field to
->Buffer offset to validate buffer length.
Security readout for executives and security teams
Plain-English summary
A flaw in the Linux kernel's ksmbd SMB file server can let a low-privileged network user submit invalid buffer offsets, potentially exposing kernel memory or disrupting the system. Integrity impact is assessed as limited. Risk is concentrated on systems actively using ksmbd and reachable by untrusted or compromised SMB accounts.
Executive priority
Prioritize remediation for reachable ksmbd servers, especially those handling sensitive data or accessible by many accounts. Other Linux systems are lower priority until ksmbd use is confirmed. No active exploitation is established by the supplied sources, but the potential confidentiality and availability consequences justify prompt, risk-based patching.
Technical view
CVE-2024-26952 is a CWE-125 out-of-bounds read caused by insufficient validation of buffer-offset fields in several ksmbd requests. The kernel fixes this by enforcing a minimum buffer-offset value before validating buffer length. CVSS 3.1 is 8.3: network-accessible, low complexity, low privileges required, no user interaction, with high confidentiality and availability impacts.
Likely exposure
Likely exposure is limited to Linux systems running ksmbd and accepting SMB requests from low-privileged users. The bundle associates affected status with multiple 5.15 through 6.9 releases, but its version representation is ambiguous; distribution package status and the relevant stable-kernel commits should determine exposure.
Exploitation context
The supplied record does not list this CVE in KEV and provides no cited evidence of active exploitation. The CVSS vector indicates exploitation requires network access and low privileges, without user interaction. Treat reachable ksmbd services and compromised SMB credentials as the primary risk context.
Researcher notes
The public description identifies invalid buffer offsets across several request types but does not establish practical exploit reliability or name those requests in the supplied text. The duplicated commit identifier and ambiguous affected-version list reduce precision. Validate branch-specific exposure against the six stable-kernel commits and distribution advisories; do not infer remote unauthenticated exploitation because CVSS specifies low privileges.
Mitigation direction
Install the vendor-supported kernel update containing the relevant stable-kernel fix.
Prioritize internet-facing or broadly reachable systems running ksmbd.
Restrict SMB access to trusted networks and authorized accounts while updates are pending.
Disable ksmbd where SMB service is unnecessary, following vendor operational guidance.
Validation and detection
Confirm whether ksmbd is enabled and serving SMB connections.
Inventory kernel and distribution package versions on systems using ksmbd.
Compare installed packages with vendor advisories and the referenced stable-kernel fixes.
Verify the updated kernel is active after installation and reboot.
Review SMB exposure and account permissions for unnecessary access.
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.
cwe · low confidence lookup
CWE-125: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
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.
2CVSS vectors
3Timeline events
2ADP providers
8Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
2 official scores
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.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-125 · source CWE mapping
Out-of-bounds Read
Out-of-bounds Read represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.