CVE-2025-21748: ksmbd: fix integer overflows on 32 bit systems
In the Linux kernel, the following vulnerability has been resolved:
ksmbd: fix integer overflows on 32 bit systems
On 32bit systems the addition operations in ipc_msg_alloc() can
potentially overflow leading to memory corruption.
Add bounds checking using KSMBD_IPC_MAX_PAYLOAD to avoid overflow.
Security readout for executives and security teams
Plain-English summary
A flaw in Linux’s ksmbd SMB server can corrupt memory on 32-bit systems when message-size calculations overflow. The supplied assessment rates it critical because network-based, unauthenticated exploitation could potentially compromise confidentiality, integrity, and availability. The sources do not establish real-world exploitation.
Executive priority
Urgently assess and patch 32-bit systems using ksmbd, prioritizing externally or broadly reachable SMB services. Systems that are 64-bit or do not use ksmbd are not identified as affected by the supplied description. Active exploitation is unconfirmed, so prioritize by verified exposure rather than CVSS alone.
Technical view
Integer additions in ksmbd’s ipc_msg_alloc() can overflow on 32-bit systems, causing an undersized allocation and potential memory corruption. The upstream correction adds bounds checking against KSMBD_IPC_MAX_PAYLOAD. The supplied CVSS 3.1 score is 9.8, with network access, low complexity, no privileges, and no user interaction.
Likely exposure
Exposure is most likely on 32-bit Linux systems using ksmbd, particularly where SMB is network-reachable. The supplied affected records span listed releases from 5.15 through 6.14, but their exact range is ambiguous. Distribution backports may alter exposure, so kernel version strings alone are insufficient.
Exploitation context
The supplied record is not in KEV, and no cited source reports active exploitation or a public exploit. The CVSS vector nevertheless describes unauthenticated network reachability and potentially complete confidentiality, integrity, and availability impact. Treat that as assessed potential, not proof of practical exploitation.
Researcher notes
The vulnerable condition is an arithmetic overflow in ipc_msg_alloc() on 32-bit architectures, followed by possible memory corruption. The correction uses KSMBD_IPC_MAX_PAYLOAD for bounds enforcement. The bundle does not document exploitability details, affected distribution package mappings, crash signatures, or whether specific ksmbd configurations change reachability.
Mitigation direction
Install a vendor-supported kernel containing the referenced upstream bounds-checking fix.
Prioritize 32-bit systems running ksmbd or exposing SMB to untrusted networks.
Consult distribution security guidance when package versions differ from upstream kernel versions.
If updating is delayed, obtain vendor guidance on supported temporary risk-reduction measures.
Validation and detection
Inventory 32-bit Linux hosts and determine whether ksmbd is installed, loaded, or active.
Identify network-reachable SMB services backed by ksmbd.
Compare running kernel packages with vendor advisories and fixed package revisions.
Confirm the installed kernel incorporates the applicable referenced stable-kernel correction.
After updating, verify systems booted into the corrected kernel.
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-21748 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
1ADP providers
8Source 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.