NTB: fix possible name leak in ntb_register_device()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ a1bd3baeb2f18b2b3d0f98ce5fdaa725149b950b · < aebfdfe39b9327a3077d0df8db3beb3160c9bdd0| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
NTB: fix possible name leak in ntb_register_device()
If device_register() fails in ntb_register_device(), the device name allocated by dev_set_name() should be freed. As per the comment in device_register(), callers should use put_device() to give up the reference in the error path. So fix this by calling put_device() in the error path so that the name can be freed in kobject_cleanup().
As a result of this, put_device() in the error path of ntb_register_device() is removed and the actual error is returned.
[mani: reworded commit message]
From the CVE record · Linux
The Linux kernel's NTB device registration can leak an allocated device name if device_register() fails. The input does not specify how an attacker could trigger the failure, or any access or user-interaction requirements.
Engineers running the Linux kernel should check their NTB device registration code; affected versions are not specified.