mISDN: fix possible memory leak in mISDN_dsp_element_register()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 1fa5ae857bb14f6046205171d98506d8112dd74e · < 7a05e3929668c8cfef495c69752a9e91fac4878f| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
mISDN: fix possible memory leak in mISDN_dsp_element_register()
Afer commit 1fa5ae857bb1 ("driver core: get rid of struct device's bus_id string array"), the name of device is allocated dynamically, use put_device() to give up the reference, so that the name can be freed in kobject_cleanup() when the refcount is 0.
The 'entry' is going to be freed in mISDN_dsp_dev_release(), so the kfree() is removed. list_del() is called in mISDN_dsp_dev_release(), so it need be initialized.
From the CVE record · Linux
The Linux kernel’s mISDN_dsp_element_register() can leak memory because a dynamically allocated device name is not freed. The input does not specify how an attacker could trigger the leak or whether authentication, local access, or user interaction is required.
Engineers running the Linux kernel should check their kernel against the vendor advisory; affected versions are not specified.