thermal: core: Fix thermal zone governor cleanup issues
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ e33df1d2f3a0141cd79e770f31999ba0dd7ebfa8 · < 75f8f3c3e09122270986de9d7aa347d701676761| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
thermal: core: Fix thermal zone governor cleanup issues
If thermal_zone_device_register_with_trips() fails after adding a thermal governor to the thermal zone being registered, the governor is not removed from it as appropriate which may lead to a memory leak.
In turn, thermal_zone_device_unregister() calls thermal_set_governor() without acquiring the thermal zone lock beforehand which may race with a governor update via sysfs and may lead to a use-after-free in that case.
Address these issues by adding two thermal_set_governor() calls, one to thermal_release() to remove the governor from the given thermal zone, and one to the thermal zone registration error path to cover failures preceding the thermal zone device registration.
From the CVE record · Linux
The Linux kernel thermal core may leak memory if thermal zone registration fails after a governor is added. Thermal zone unregistration can also race with a governor update through sysfs, potentially causing a use-after-free. The input does not specify authentication requirements or an attacker-controlled trigger.
Teams running the Linux kernel should check whether their kernel includes the thermal core fix; affected versions are not specified.