media: solo6x10: fix possible memory leak in solo_sysfs_init()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ dcae5dacbce518513abf7776cb450b7bd95d722b · < 7cf71bbe5d2ee12613f6e278888f5fc9c5c0cc2b| No fix yet |
| Linux Linux |
|
|
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().
From the CVE record · Linux
The Linux kernel's solo6x10 driver can leak memory if device registration fails during solo_sysfs_init(). The input does not describe how an attacker could trigger the failure or specify network access, authentication, or user-interaction requirements.
Engineers running Linux kernels with the solo6x10 driver should check their versions; affected versions are not specified in the input.