CVE-2025-38090: drivers/rapidio/rio_cm.c: prevent possible heap overwrite
In the Linux kernel, the following vulnerability has been resolved:
drivers/rapidio/rio_cm.c: prevent possible heap overwrite
In
riocm_cdev_ioctl(RIO_CM_CHAN_SEND)
-> cm_chan_msg_send()
-> riocm_ch_send()
cm_chan_msg_send() checks that userspace didn't send too much data but
riocm_ch_send() failed to check that userspace sent sufficient data. The
result is that riocm_ch_send() can write to fields in the rio_ch_chan_hdr
which were outside the bounds of the space which cm_chan_msg_send()
allocated.
Address this by teaching riocm_ch_send() to check that the entire
rio_ch_chan_hdr was copied in from userspace.
Security readout for executives and security teams
Plain-English summary
A low-privileged local user may be able to trigger a heap overwrite in the Linux kernel’s RapidIO connection-management driver. Successful exploitation could compromise confidentiality, integrity, and availability. The issue is serious where RapidIO support and its character-device interface are present, but it is not described as remotely exploitable.
Executive priority
Prioritize prompt remediation on multi-user or less-trusted Linux systems using RapidIO. Other systems should be inventoried and validated before emergency action. Treat as high impact but not an internet-wide remote emergency based on the supplied evidence.
Technical view
The RIO_CM_CHAN_SEND ioctl path validated the maximum message size but not whether userspace supplied enough data for a complete rio_ch_chan_hdr. riocm_ch_send() could consequently write header fields beyond the allocated heap buffer. The kernel fix verifies that the complete header was copied before those fields are written.
Likely exposure
Exposure likely requires a vulnerable Linux kernel, the RapidIO connection-management driver and device interface, and local low-privileged access. Systems without this driver or accessible interface are less likely to be exposed. The supplied version list is insufficiently precise for reliable range interpretation, so confirm status against the running distribution kernel.
Exploitation context
The CVSS vector rates exploitation as local, low complexity, requiring low privileges and no user interaction, with potentially high confidentiality, integrity, and availability impact. The source bundle states KEV is false and provides no evidence of active exploitation or a public exploit.
Researcher notes
The vulnerable path is riocm_cdev_ioctl(RIO_CM_CHAN_SEND) through cm_chan_msg_send() to riocm_ch_send(). The defect is an undersized-input validation failure leading to an out-of-bounds heap write. The bundle contains duplicate commit identifiers and flattened version data, limiting precise affected-range conclusions.
Mitigation direction
Install the applicable vendor or distribution kernel security update containing the upstream fix.
If patching is delayed, assess whether RapidIO support can be disabled without operational impact.
Restrict local account and device-interface access according to least privilege.
Check current Linux distribution advisories for supported-package remediation guidance.
Validation and detection
Record each system’s running kernel release, build, and distribution package version.
Determine whether the RapidIO connection-management driver is built, loaded, or operationally required.
Verify which users can access the relevant RapidIO character-device interface.
Confirm the installed kernel includes the applicable upstream fix or distribution backport.
After updating, reboot into the corrected kernel and verify the running version.
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-38090 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
11Source 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.