Kernel memory leak via incomplete class cleanup
Published Oct 22, 2025 · Updated Oct 22, 2025
Memory leakage in the device-class core in the Linux kernel allows attackers to consume kernel memory through failed class registration. When class_add_groups() fails, __class_register() neither removes cp->subsys nor frees the class-private object and its retained name. The published reproduction uses fault injection during modprobe, and public sources establish no attacker-controlled input or effect beyond unreclaimed kernel memory.
Summary
What happened
Memory leakage in the device-class core in the Linux kernel allows attackers to consume kernel memory through failed class registration. When class_add_groups() fails, __class_register() neither removes cp->subsys nor frees the class-private object and its retained name. The published reproduction uses fault injection during modprobe, and public sources establish no attacker-controlled input or effect beyond unreclaimed kernel memory.
The record
- CVE
- CVE-2022-50578
- Published
- Oct 22, 2025
- Updated
- Oct 22, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Oct 22, 2025CVE publishedPublication date reported by the CVE source.
- Oct 22, 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=4.10
- Affected versionversion=ced6473e7486702f530a49f886b73195e4977734 <18a7200646958cf8e1b8a933de08122fc50676cd
- Affected versionversion=ced6473e7486702f530a49f886b73195e4977734 <3bb9c92c27624ad076419a70f2b1a30cd1f8bbbd
- Affected versionversion=ced6473e7486702f530a49f886b73195e4977734 <3e0efc3f3f5e5c73996782f8db69963e501bb878
- Affected versionversion=ced6473e7486702f530a49f886b73195e4977734 <417ef049e3fd3b0d2593c1d5ffa3d0d5d0a018a7
- Affected versionversion=ced6473e7486702f530a49f886b73195e4977734 <4efa5443817c1b6de22d401aeca5b2481e835f8c
- Affected versionversion=ced6473e7486702f530a49f886b73195e4977734 <8c3e8a6bdb5253b97ad532570f8b5db5f7a06407
- Affected versionversion=ced6473e7486702f530a49f886b73195e4977734 <abaedb68a769e6bf36836b55a2f49b531c5f3f7b
- Affected versionversion=ced6473e7486702f530a49f886b73195e4977734 <e764ad5918a099ebeb909ccff83893a714e497e1
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