hwmon: (lm90) Stop work before releasing hwmon device
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ f6d0775119fb905fb02eafa98d575cf8ee792d46 · < b09a45601094c7f4ec4db8090b825fa61e169d93| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
hwmon: (lm90) Stop work before releasing hwmon device
Sashiko reports:
In lm90_probe(), the devm action to cancel the alert_work and report_work (lm90_restore_conf) is registered in lm90_init_client() before devm_hwmon_device_register_with_info() is called.
Because devm executes cleanup actions in reverse order during module unbind or probe failure, the hwmon device is unregistered and freed first.
If lm90_alert_work() or lm90_report_alarms() runs in the window between the hwmon device being freed and the delayed works being cancelled, lm90_update_alarms() will dereference the freed data->hwmon_dev here.
Fix the problem by canceling the workers separately after registering the hwmon device and before registering the interrupt handler. This ensures that the workers are canceled after interrupts are disabled and before the hwmon device is released. Add "shutdown" flag to indicate that device shutdown is in progress to prevent workers from being re-armed.
From the CVE record · Linux
The Linux kernel’s lm90 hwmon driver can dereference a freed hwmon device if delayed work runs during module unbind or probe failure. The input does not establish whether an attacker can trigger this condition, or whether network access, authentication, or user interaction is required.
Engineers running Linux kernels with the lm90 hwmon driver should check their kernel versions; affected versions are not specified.