NTB: fix possible name leak in ntb_register_device()
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 6632a54ac8057cc0b0d789c6f73883e871bcd25c, Kernel 913421f9f7fd8324dcc41753d0f28b52e177ef04, Kernel a039690d323221eb5865f1f31db3ec264e7a14b6 and 3 more.
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]
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =4.2, >=a1bd3baeb2f18b2b3d0f98ce5fdaa725149b950b <6632a54ac8057cc0b0d789c6f73883e871bcd25c, >=a1bd3baeb2f18b2b3d0f98ce5fdaa725149b950b <913421f9f7fd8324dcc41753d0f28b52e177ef04, >=a1bd3baeb2f18b2b3d0f98ce5fdaa725149b950b <a039690d323221eb5865f1f31db3ec264e7a14b6, >=a1bd3baeb2f18b2b3d0f98ce5fdaa725149b950b <a62b9f3d7bbfac874cc0c638bc1776dcf1f8ec06, >=a1bd3baeb2f18b2b3d0f98ce5fdaa725149b950b <aebfdfe39b9327a3077d0df8db3beb3160c9bdd0, >=a1bd3baeb2f18b2b3d0f98ce5fdaa725149b950b <e8025439ef8e16029dc313d78a351ef192469b7b | 6632a54ac8057cc0b0d789c6f73883e871bcd25c, 913421f9f7fd8324dcc41753d0f28b52e177ef04, a039690d323221eb5865f1f31db3ec264e7a14b6, a62b9f3d7bbfac874cc0c638bc1776dcf1f8ec06, aebfdfe39b9327a3077d0df8db3beb3160c9bdd0, e8025439ef8e16029dc313d78a351ef192469b7b |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket