Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2025-38090drivers/rapidio/rio_cm.c: prevent possible heap overwrite

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. · 3 months later

    Published

  3. · 13 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2025-38090, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.20% · top 90% of all CVEs (19 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.

Affected products

  • Linux · Linux

    • affected b6e8d4aa1110306378af0f3472a6b85a1f039a16 – < a8b5ea2e302aa5cd00fc7addd8df53c9bde7b5f6
    • affected b6e8d4aa1110306378af0f3472a6b85a1f039a16 – < c03ddc183249f03fc7e057e02cae6f89144d0123
    • affected b6e8d4aa1110306378af0f3472a6b85a1f039a16 – < 58f664614f8c3d6142ab81ae551e466dc6e092e8
    • affected b6e8d4aa1110306378af0f3472a6b85a1f039a16 – < ecf5ee280b702270afb02f61b299d3dfe3ec7730
    • affected b6e8d4aa1110306378af0f3472a6b85a1f039a16 – < 1921781ec4a8824bd0c520bf9363e28a880d14ec
    • affected b6e8d4aa1110306378af0f3472a6b85a1f039a16 – < 1cce6ac47f4a2ac1766b8a188dc8c8f6d8df2a53
    • affected b6e8d4aa1110306378af0f3472a6b85a1f039a16 – < 6d5c6711a55c35ce09b90705546050408d9d4b61
    • affected b6e8d4aa1110306378af0f3472a6b85a1f039a16 – < 50695153d7ddde3b1696dbf0085be0033bf3ddb3
  • Linux · Linux

    • affected 4.8
    • unaffected < 4.8
    • unaffected 5.4.295 – ≤ 5.4.*
    • unaffected 5.10.239 – ≤ 5.10.*
    • unaffected 5.15.186 – ≤ 5.15.*
    • unaffected 6.1.142 – ≤ 6.1.*
    • unaffected 6.6.95 – ≤ 6.6.*
    • unaffected 6.12.35 – ≤ 6.12.*
    • unaffected 6.15.4 – ≤ 6.15.*
    • unaffected 6.16 – ≤ *

References

References10

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2025-38090 badge
[![CVE-2025-38090](https://cveledger.app/badge/CVE-2025-38090.svg)](https://cveledger.app/cve/CVE-2025-38090)

Record last updated .