Vulnerability · CVE-2022-50547
In the Linux kernel, the following vulnerability has been resolved: media: solo6x10: fix possible memory leak in solo_sysfs_init() If device_register() returns error in solo_sysfs_
Published Oct 7, 2025 · catalog updated May 11, 2026 · Linux Linux
Check this week
CVE-2022-50547 is not in CISA KEV. FIRST estimates a 20.00% chance of exploitation in the next 30 days. Check whether you run Linux Linux.
Gaps on this record
- No vendor fix or required action is stored. Compare the linked advisory before you change production.
- Severity
- None0.0
- Known exploitation
- Not in CISA/VulnCheck KEV
- EPSS
- 20.00%
- Remediation
- Version ranges on file
- Affected products
- vendor Linux Linux dcae5dacbce518513abf7776cb450b7bd95d722b <963729538674be4cb8fa292529ecf32de0d6c6dd
In the Linux kernel, the following vulnerability has been resolved: media: solo6x10: fix possible memory leak in solo_sysfs_init() If device_register() returns error in solo_sysfs_init(), the name allocated by dev_set_name() need be freed. As comment of device_register() says, it should use put_device() to give up the reference in the error path. So fix this by calling put_device(), then the name can be freed in kobject_cleanup().
Are you affected?
Enter the version you run. The result uses only the ranges stored on this record.
The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.
- vendor Linux Linux dcae5dacbce518513abf7776cb450b7bd95d722b <963729538674be4cb8fa292529ecf32de0d6c6dddcae5dacbce518513abf7776cb450b7bd95d722b <963729538674be4cb8fa292529ecf32de0d6c6dd
How to fix CVE-2022-50547
Recommended remediation
Affected version ranges suggest a fixed boundary. Verify against the vendor advisory for your release.
Official advisories
What to do
Three questions, each answered from this record only. Confirm the vendor advisory before you patch.
Should you patch?
CVE-2022-50547 is not in CISA KEV. FIRST estimates a 20.00% chance of exploitation in the next 30 days. Check whether you run Linux Linux.
Which versions are affected?
Compare what you have installed with Linux Linux dcae5dacbce518513abf7776cb450b7bd95d722b <963729538674be4cb8fa292529ecf32de0d6c6dd dcae5dacbce518513abf7776cb450b7bd95d722b <963729538674be4cb8fa292529ecf32de0d6c6dd. Compare the installed version with the linked vendor advisory before you change production.
What should an analyst verify?
No weakness class is stored. EPSS 20.00%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.
Code
The project this record applies to. Exploit listings stay in References.
Timeline
Detection, updates, and resolution for this record.
Oct 7, 2025 · EUVD
Detected
In the Linux kernel, the following vulnerability has been resolved: media: solo6x10: fix possible memory leak in solo_sysfs_init() If device_register() returns error in solo_sysfs_init(), the name allocated by dev_set_name() need be freed. As comment of device_register() says, it should use put_device() to give up the reference in the error path. So fix this by calling put_device(), then the name
May 11, 2026 · EUVD
Updated
In the Linux kernel, the following vulnerability has been resolved: media: solo6x10: fix possible memory leak in solo_sysfs_init() If device_register() returns error in solo_sysfs_init(), the name allocated by dev_set_name() need be freed. As comment of device_register() says, it should use put_device() to give up the reference in the error path. So fix this by calling put_device(), then the name
Sources
- CVE.orgVulnerability recordCVE-2022-50547
Official CVE identifier
cve.org - EUVDVulnerability recordEUVD-2025-32012
In the Linux kernel, the following vulnerability has been resolved: media: solo6x10: fix possible memory leak in solo_sysfs_init() If device_register() returns error in solo_sysfs_init(), the name allocated by dev_set_name() need be freed. As comment of device_register() says, it
euvd.enisa.europa.eu
References
Freshness
Last verified in this catalog May 11, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.