hwmon: (lm90) Add lock protection to lm90_alert
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 7a1d220ccb0cc2b808eb176fb05bf55a38179f3f · < 873e919e3101063a7a75989510ccfc125a4391cf| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
hwmon: (lm90) Add lock protection to lm90_alert
Sashiko reports:
lm90_alert() executes in the smbus alert context and calls lm90_update_confreg() to disable the hardware alert line, without acquiring hwmon_lock.
Concurrently, sysfs write operations (such as lm90_write_convrate) hold the hwmon_lock, temporarily modify data->config, and then restore it.
If an alert interrupt occurs concurrently with a sysfs write, the sysfs path will overwrite the alert handler's modifications to data->config and the hardware register.
This unintentionally re-enables the hardware alert line while the alarm is still active, causing an interrupt storm.
Add the missing lock to lm90_alert() to solve the problem.
From the CVE record · Linux
The lm90 hardware-monitoring driver does not lock its alert handler when updating the device configuration. If an alert occurs during a sysfs write, the write can re-enable the alert line while the alarm is active, causing an interrupt storm. The input does not specify authentication requirements or whether an attacker can trigger this condition.
Engineers running Linux kernels with the lm90 hwmon driver should check their kernel vendor’s advisory for affected versions.