Local denial of service via registration memory leak
Published Oct 7, 2025 · Updated Oct 7, 2025
Memory leakage in the solo6x10 media driver in affected Linux kernel releases allows local users to exhaust kernel memory. The solo_sysfs_init error path retains the device reference when device_register fails, so the name allocated by dev_set_name is never released through kobject cleanup. The condition requires initialization of a supported Solo6x10 PCI capture card and a device-registration failure; no remote path is reported.
Summary
What happened
Memory leakage in the solo6x10 media driver in affected Linux kernel releases allows local users to exhaust kernel memory. The solo_sysfs_init error path retains the device reference when device_register fails, so the name allocated by dev_set_name is never released through kobject cleanup. The condition requires initialization of a supported Solo6x10 PCI capture card and a device-registration failure; no remote path is reported.
The record
- CVE
- CVE-2022-50547
- Published
- Oct 7, 2025
- Updated
- Oct 7, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-401
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 7, 2025CVE publishedPublication date reported by the CVE source.
- Oct 7, 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=3.10
- Affected versionversion=dcae5dacbce518513abf7776cb450b7bd95d722b <49060c0da57a381563e482e331dc9d4c3725b41b
- Affected versionversion=dcae5dacbce518513abf7776cb450b7bd95d722b <7b02c50d3978840781808e13bc13137fb81286b5
- Affected versionversion=dcae5dacbce518513abf7776cb450b7bd95d722b <7cf71bbe5d2ee12613f6e278888f5fc9c5c0cc2b
- Affected versionversion=dcae5dacbce518513abf7776cb450b7bd95d722b <7f5866dd96d95b74e439f6ee17b8abd8195179fb
- Affected versionversion=dcae5dacbce518513abf7776cb450b7bd95d722b <83d4b1ae98a47a739fa5241300b86eb1110d5d63
- Affected versionversion=dcae5dacbce518513abf7776cb450b7bd95d722b <9416861170ba0da8ddb0f4fd2d28334f0ed3b9c2
- Affected versionversion=dcae5dacbce518513abf7776cb450b7bd95d722b <963729538674be4cb8fa292529ecf32de0d6c6dd
- Affected versionversion=dcae5dacbce518513abf7776cb450b7bd95d722b <b61509093e1af69e336a094d439b8e1137cb40d8
- Affected versionversion=dcae5dacbce518513abf7776cb450b7bd95d722b <d6db105bcfbdbbbd484e788a0ddf8140a4a8c486
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
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