Local service interruption via unchecked RapidIO registration
Published Apr 1, 2025 · Updated May 11, 2026
Improper error handling in Linux kernel 4.6 and later allows local users to interrupt service through the RapidIO subsystem. rio_scan_alloc_net() ignores a rio_add_net() failure, retaining allocated memory and its initialized device reference instead of calling put_device(). Exploitation requires local low-privileged access and a RapidIO scan path in which device registration fails; confidentiality and integrity effects are not reported.
Summary
What happened
Improper error handling in Linux kernel 4.6 and later allows local users to interrupt service through the RapidIO subsystem. rio_scan_alloc_net() ignores a rio_add_net() failure, retaining allocated memory and its initialized device reference instead of calling put_device(). Exploitation requires local low-privileged access and a RapidIO scan path in which device registration fails; confidentiality and integrity effects are not reported.
The record
- CVE
- CVE-2025-21935
- Published
- Apr 1, 2025
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 1, 2025CVE publishedPublication date reported by the CVE source.
- May 11, 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.6
- Affected versionversion=e6b585ca6e81badeb3d42db3cc408174f2826034 <181d4daaefb3bceeb2f2635ba9f3781eeda9e550
- Affected versionversion=e6b585ca6e81badeb3d42db3cc408174f2826034 <4f3509cfcc02e9d757f2714bb7dbbeec35de6fa7
- Affected versionversion=e6b585ca6e81badeb3d42db3cc408174f2826034 <6d22953c4a183d0b7fdf34d68c5debd16da6edc5
- Affected versionversion=e6b585ca6e81badeb3d42db3cc408174f2826034 <a0d069ccc475abaaa79c6368ee27fc0b5912bea8
- Affected versionversion=e6b585ca6e81badeb3d42db3cc408174f2826034 <ad82be4298a89a9ae46f07128bdf3d8614bce745
- Affected versionversion=e6b585ca6e81badeb3d42db3cc408174f2826034 <c332f3e2df0fcae5a45fd55cc18902fb1e4825ca
- Affected versionversion=e6b585ca6e81badeb3d42db3cc408174f2826034 <e6411c3b9512dba09af7d014d474516828c89706
- Affected versionversion=e6b585ca6e81badeb3d42db3cc408174f2826034 <e842f9a1edf306bf36fe2a4d847a0b0d458770de
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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
No sourced classifications are available.
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