siox: fix possible memory leak in siox_device_add()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ bbecb07fa0af9a41507ce06d4631fdb3b5059417 · < 6e63153db50059fb78b8a8447b132664887d24e3| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
siox: fix possible memory leak in siox_device_add()
If device_register() returns error in siox_device_add(), 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(), and sdevice is freed in siox_device_release(), set it to null in error path.
From the CVE record · Linux
The Linux kernel's siox_device_add() can leak memory when device_register() fails. The input does not establish whether an attacker can trigger the failure, or specify any access or user-interaction requirements.
Engineers running Linux kernels with the siox component should check their vendor's advisory; affected versions are not specified.