LiveActive security incident?Get immediate response
CVE Record

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.

HighCVSS 7.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

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.
Prepared
Confidence
medium
Sources
6

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.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9Linux

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2025-38090Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxb6e8d4aa1110306378af0f3472a6b85a1f039a16, b6e8d4aa1110306378af0f3472a6b85a1f039a16, b6e8d4aa1110306378af0f3472a6b85a1f039a16, b6e8d4aa1110306378af0f3472a6b85a1f039a16, b6e8d4aa1110306378af0f3472a6b85a1f039a16, b6e8d4aa1110306378af0f3472a6b85a1f039a16, b6e8d4aa1110306378af0f3472a6b85a1f039a16, b6e8d4aa1110306378af0f3472a6b85a1f039a16unaffected
LinuxLinux4.8, 0, 5.4.295, 5.10.239, 5.15.186, 6.1.142, 6.6.95, 6.12.35, 6.15.4, 6.16affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.