CVE-2025-38090
What it is
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.
At a glance
- Exploitability
- Can be exploited locally on the machine with a low-privilege account. High risk of data exposure, data tampering, service disruption.
- Exploit odds
- 0.2% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.2% in the next 30 days (EPSS).
- Severity: 7.8 HIGH (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.2% · EPSS, next 30 days
- Record status
- Modified
Affected
- Linux Kernel < 5.4.295
- Linux Kernel < 5.10.239
- Linux Kernel < 5.15.186
- Linux Kernel < 6.1.142
- Linux Kernel < 6.6.95
- Linux Kernel < 6.12.35
- Linux Kernel < 6.15.4
- Linux Kernel 6.16
Attack profile CVSS 3.1 · 7.8
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2025-38090.md and follow it. Check whether this project is affected by CVE-2025-38090. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://git.kernel.org/stable/c/1921781ec4a8824bd0c520bf9363e28a880d14ec
- https://git.kernel.org/stable/c/1cce6ac47f4a2ac1766b8a188dc8c8f6d8df2a53
- https://git.kernel.org/stable/c/50695153d7ddde3b1696dbf0085be0033bf3ddb3
- https://git.kernel.org/stable/c/58f664614f8c3d6142ab81ae551e466dc6e092e8
- https://git.kernel.org/stable/c/6d5c6711a55c35ce09b90705546050408d9d4b61
- https://git.kernel.org/stable/c/a8b5ea2e302aa5cd00fc7addd8df53c9bde7b5f6
- https://git.kernel.org/stable/c/c03ddc183249f03fc7e057e02cae6f89144d0123
- https://git.kernel.org/stable/c/ecf5ee280b702270afb02f61b299d3dfe3ec7730
References
- https://git.kernel.org/stable/c/1921781ec4a8824bd0c520bf9363e28a880d14ec
- https://git.kernel.org/stable/c/1cce6ac47f4a2ac1766b8a188dc8c8f6d8df2a53
- https://git.kernel.org/stable/c/50695153d7ddde3b1696dbf0085be0033bf3ddb3
- https://git.kernel.org/stable/c/58f664614f8c3d6142ab81ae551e466dc6e092e8
- https://git.kernel.org/stable/c/6d5c6711a55c35ce09b90705546050408d9d4b61
- https://git.kernel.org/stable/c/a8b5ea2e302aa5cd00fc7addd8df53c9bde7b5f6
- https://git.kernel.org/stable/c/c03ddc183249f03fc7e057e02cae6f89144d0123
- https://git.kernel.org/stable/c/ecf5ee280b702270afb02f61b299d3dfe3ec7730
- https://lists.debian.org/debian-lts-announce/2025/10/msg00007.html
- https://lists.debian.org/debian-lts-announce/2025/10/msg00008.html