scsi: target: tcm_loop: Fix possible name leak in tcm_loop_setup_hba_bus()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 3703b2c5d041a68095cdd22380c23ce27d449ad7 · < bc68e428d4963af0201e92159629ab96948f0893| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
scsi: target: tcm_loop: Fix possible name leak in tcm_loop_setup_hba_bus()
If device_register() fails in tcm_loop_setup_hba_bus(), 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(). The 'tl_hba' will be freed in tcm_loop_release_adapter(), so it don't need goto error label in this case.
From the CVE record · Linux
The Linux kernel’s tcm_loop component can leak an allocated device name if device_register() fails during tcm_loop_setup_hba_bus(). The input does not establish how an attacker could trigger this failure or whether network access, authentication, or user interaction is required.
Engineers running Linux kernels with the tcm_loop component should check whether their kernel is affected; affected versions are not specified.