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_init(), the name allocated by dev_set_name() need be freed.
Does this matter?
Lower severity and a low EPSS score (0.20%). Track it; it rarely justifies an emergency change on its own.
Description
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().
- CVSS 3.1
- 5.5 MEDIUMCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
- EPSS
- 0.20% probability · 11th percentile
- CISA KEV
- Not listed
- Weakness
- CWE-401
- Affected
- linux/linux kernel
- Source
- 416baaa9-dc9f-4396-8d5f-8c081fb06d67
References
- https://git.kernel.org/stable/c/49060c0da57a381563e482e331dc9d4c3725b41bPatch
- https://git.kernel.org/stable/c/7b02c50d3978840781808e13bc13137fb81286b5Patch
- https://git.kernel.org/stable/c/7cf71bbe5d2ee12613f6e278888f5fc9c5c0cc2bPatch
- https://git.kernel.org/stable/c/7f5866dd96d95b74e439f6ee17b8abd8195179fbPatch
- https://git.kernel.org/stable/c/83d4b1ae98a47a739fa5241300b86eb1110d5d63Patch
- https://git.kernel.org/stable/c/9416861170ba0da8ddb0f4fd2d28334f0ed3b9c2Patch
- https://git.kernel.org/stable/c/963729538674be4cb8fa292529ecf32de0d6c6ddPatch
- https://git.kernel.org/stable/c/b61509093e1af69e336a094d439b8e1137cb40d8Patch
- https://git.kernel.org/stable/c/d6db105bcfbdbbbd484e788a0ddf8140a4a8c486Patch
Source: NVD record, EPSS from FIRST.org, KEV from CISA. Refreshed daily.