CVE-2022-50547
media: solo6x10: fix possible memory leak in solo_sysfs_init()
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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().
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
Version range not reported
- Linux Linux
3.10
References 9
git.kernel.org
- stable/c/83d4b1ae98a47a739fa5241300b86eb1110d5d63
- stable/c/b61509093e1af69e336a094d439b8e1137cb40d8
- stable/c/963729538674be4cb8fa292529ecf32de0d6c6dd
- stable/c/7b02c50d3978840781808e13bc13137fb81286b5
- stable/c/49060c0da57a381563e482e331dc9d4c3725b41b
- stable/c/7cf71bbe5d2ee12613f6e278888f5fc9c5c0cc2b
- stable/c/d6db105bcfbdbbbd484e788a0ddf8140a4a8c486
- stable/c/9416861170ba0da8ddb0f4fd2d28334f0ed3b9c2
- stable/c/7f5866dd96d95b74e439f6ee17b8abd8195179fb