rapidio: fix possible name leaks when rio_add_device() fails
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 1fa5ae857bb14f6046205171d98506d8112dd74e · < ec3f04f74f50d0b6bac04d795c93c2b852753a7a| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
rapidio: fix possible name leaks when rio_add_device() fails
Patch series "rapidio: fix three possible memory leaks".
This patchset fixes three name leaks in error handling. - patch #1 fixes two name leaks while rio_add_device() fails. - patch #2 fixes a name leak while rio_register_mport() fails.
This patch (of 2):
If rio_add_device() returns error, the name allocated by dev_set_name() need be freed. It should use put_device() to give up the reference in the error path, so that the name can be freed in kobject_cleanup(), and the 'rdev' can be freed in rio_release_dev().
From the CVE record · Linux
The Linux kernel’s RapidIO code can leak a device name when rio_add_device() fails. The input does not establish how an attacker could trigger the failure or whether access or user interaction is required.
Engineers running Linux kernels with RapidIO support should check their kernel versions; affected versions are not specified.