CVE-2022-50547

low-risk
Published 2025-10-07

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().

Do I need to act?

-
0.03% chance of exploitation
EPSS score — low exploit probability
-
Not on CISA KEV list
No confirmed active exploitation reported to CISA
?
Patch status unknown
Check vendor advisories for fix availability and mitigation guidance
5
CVSS 5.5/10 Medium
LOCAL / LOW complexity

Affected Products (1)

Affected Vendors

Linux

References (9)

Patch https://git.kernel.org/stable/c/49060c0da57a381563e482e331dc9d4c3725b41b
Patch https://git.kernel.org/stable/c/7b02c50d3978840781808e13bc13137fb81286b5
Patch https://git.kernel.org/stable/c/7cf71bbe5d2ee12613f6e278888f5fc9c5c0cc2b
Patch https://git.kernel.org/stable/c/7f5866dd96d95b74e439f6ee17b8abd8195179fb
Patch https://git.kernel.org/stable/c/83d4b1ae98a47a739fa5241300b86eb1110d5d63
Patch https://git.kernel.org/stable/c/9416861170ba0da8ddb0f4fd2d28334f0ed3b9c2
Patch https://git.kernel.org/stable/c/963729538674be4cb8fa292529ecf32de0d6c6dd
Patch https://git.kernel.org/stable/c/b61509093e1af69e336a094d439b8e1137cb40d8
Patch https://git.kernel.org/stable/c/d6db105bcfbdbbbd484e788a0ddf8140a4a8c486
23
/ 100
low-risk
Severity 18/34 · Moderate
Exploitability 0/34 · Minimal
Exposure 5/34 · Minimal