Kernel heap corruption via undersized RapidIO channel message
Published Jun 30, 2025 · Updated Aug 5, 2026
Out-of-bounds write in Linux 4.8 and later allows local users to corrupt kernel heap memory through a crafted RapidIO channel-send ioctl. riocm_ch_send() accepts a buffer shorter than rio_ch_chan_hdr, then writes header fields beyond the heap allocation made by cm_chan_msg_send(). The caller needs access to the RapidIO character device and a connected channel; triggering the flaw overwrites adjacent kernel heap memory.
Summary
What happened
Out-of-bounds write in Linux 4.8 and later allows local users to corrupt kernel heap memory through a crafted RapidIO channel-send ioctl. riocm_ch_send() accepts a buffer shorter than rio_ch_chan_hdr, then writes header fields beyond the heap allocation made by cm_chan_msg_send(). The caller needs access to the RapidIO character device and a connected channel; triggering the flaw overwrites adjacent kernel heap memory.
The record
- CVE
- CVE-2025-38090
- Published
- Jun 30, 2025
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 30, 2025CVE publishedPublication date reported by the CVE source.
- Aug 5, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=4.8
- Affected versionversion=b6e8d4aa1110306378af0f3472a6b85a1f039a16 <1921781ec4a8824bd0c520bf9363e28a880d14ec
- Affected versionversion=b6e8d4aa1110306378af0f3472a6b85a1f039a16 <1cce6ac47f4a2ac1766b8a188dc8c8f6d8df2a53
- Affected versionversion=b6e8d4aa1110306378af0f3472a6b85a1f039a16 <50695153d7ddde3b1696dbf0085be0033bf3ddb3
- Affected versionversion=b6e8d4aa1110306378af0f3472a6b85a1f039a16 <58f664614f8c3d6142ab81ae551e466dc6e092e8
- Affected versionversion=b6e8d4aa1110306378af0f3472a6b85a1f039a16 <6d5c6711a55c35ce09b90705546050408d9d4b61
- Affected versionversion=b6e8d4aa1110306378af0f3472a6b85a1f039a16 <a8b5ea2e302aa5cd00fc7addd8df53c9bde7b5f6
- Affected versionversion=b6e8d4aa1110306378af0f3472a6b85a1f039a16 <c03ddc183249f03fc7e057e02cae6f89144d0123
- Affected versionversion=b6e8d4aa1110306378af0f3472a6b85a1f039a16 <ecf5ee280b702270afb02f61b299d3dfe3ec7730
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo