Kernel memory leak via failed port registration
Published Dec 30, 2025 · Updated Dec 30, 2025
Memory leak in affected Linux kernel branches beginning with 3.15 allows attackers to retain kernel memory after failed RapidIO port registration. The rio_register_mport() error path omits put_device(), leaving the dev_set_name() allocation and rio_mports list entry unreleased. The public record does not identify how an attacker can force the registration failure or quantify whether repeated leaks can interrupt service.
Summary
What happened
Memory leak in affected Linux kernel branches beginning with 3.15 allows attackers to retain kernel memory after failed RapidIO port registration. The rio_register_mport() error path omits put_device(), leaving the dev_set_name() allocation and rio_mports list entry unreleased. The public record does not identify how an attacker can force the registration failure or quantify whether repeated leaks can interrupt service.
The record
- CVE
- CVE-2022-50857
- Published
- Dec 30, 2025
- Updated
- Dec 30, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Dec 30, 2025CVE publishedPublication date reported by the CVE source.
- Dec 30, 2025Record 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=2aaf308b95b24649a6dcfed89cd956e972089b2a <0a71344f99289250e4d5b8adbac76f444485c840
- Affected versionversion=2aaf308b95b24649a6dcfed89cd956e972089b2a <117fede82e9d6ea3de30746d500eb5edc2eb8310
- Affected versionversion=2aaf308b95b24649a6dcfed89cd956e972089b2a <1bbad5793f404cf218757e3beb600eca6080330f
- Affected versionversion=2aaf308b95b24649a6dcfed89cd956e972089b2a <4ddbeae5f224d924cf0b12460dda88c7480aa452
- Affected versionversion=2aaf308b95b24649a6dcfed89cd956e972089b2a <97d9eb45ffa67ffa112a6659953321b8f7db0065
- Affected versionversion=2aaf308b95b24649a6dcfed89cd956e972089b2a <9abba4aa60874c5216fc8de7dededadc791de696
- Affected versionversion=2aaf308b95b24649a6dcfed89cd956e972089b2a <a47de2fd3f88a7788be19f94ade72c2244a98045
- Affected versionversion=2aaf308b95b24649a6dcfed89cd956e972089b2a <a73a626c0510d203e369aeb26c4d6ec9c75af027
- Affected versionversion=2aaf308b95b24649a6dcfed89cd956e972089b2a <e92a216d16bde65d21a3227e0fb2aa0794576525
- Affected versionversion=3.15
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
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