hwmon: chipcap2: fix IRQ teardown ordering
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel a205f2113200c6357e0526c94caaa4c2aceb2fc7, Kernel d2a66c515d7730fd453485ffb306c412f1f46d72 and Kernel 7.3.5.
In the Linux kernel, the following vulnerability has been resolved: hwmon: chipcap2: fix IRQ teardown ordering The threaded IRQs are currently requested before the hwmon device is registered. Since devres releases resources in reverse order, the hwmon device is unregistered before the IRQs are freed during driver teardown. An IRQ may therefore still run after the hwmon device has been released and access the stale data->hwmon pointer. Separate IRQ discovery from IRQ registration so that the IRQ numbers and alarm visibility flags are initialized before registering the hwmon device while the IRQs are released before the hwmon device during devres cleanup.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =6.9, >=3af350929e752fe72f0457033d448bff9aac695a <a205f2113200c6357e0526c94caaa4c2aceb2fc7, >=3af350929e752fe72f0457033d448bff9aac695a <d2a66c515d7730fd453485ffb306c412f1f46d72 | a205f2113200c6357e0526c94caaa4c2aceb2fc7, d2a66c515d7730fd453485ffb306c412f1f46d72 |
| linux-kernel: Kernel | >=6.9.0 <7.3.5 | 7.3.5 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket