thermal: hwmon: Remove hwmon class device along with its parent
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ f6b6b52ef7a54160c0a4d2b56a58f84a2e5b33c5 · < 2b57e24d34b2dfc43c81942bb359d6315bf302fb| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
thermal: hwmon: Remove hwmon class device along with its parent
The current code creates one hwmon device per thermal zone type and that device is registered under the first thermal zone of the given type.
That turns out to be problematic when the thermal zone holding the hwmon device is removed.
For example, say that there are two ACPI thermal zones on a system
/sys/devices/virtual/thermal/thermal_zone0/ /sys/devices/virtual/thermal/thermal_zone1/
The current code registers a hwmon class device for thermal_zone0 only:
/sys/devices/virtual/thermal/thermal_zone0/hwmon0/
From the CVE record · Linux
The Linux kernel thermal hwmon interface can prevent a thermal zone from being removed when its hwmon device also contains an attribute belonging to another zone of the same type. This can occur when the zone holding the hwmon device is removed, such as when the ACPI thermal driver is unbound; the input does not describe an attacker, access requirements, or user interaction.
Engineers running Linux kernels with thermal zones that use the hwmon interface should check their systems; affected versions are not specified.