power: supply: rt9455: quiesce delayed work before teardown
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel df67c7a2fff8414aa766b8cd5ffe11ec1ca27d02, Kernel 1b9978433c61a9b46e48832a1ebceee1cf5c9eb4, Kernel 3def4721431f3e374e1e3124f4d32bb07ae8df1c and 12 more.
In the Linux kernel, the following vulnerability has been resolved: power: supply: rt9455: quiesce delayed work before teardown The threaded IRQ handler can queue pwr_rdy_work, max_charging_time_work and batt_presence_work. pwr_rdy_work and batt_presence_work can also queue max_charging_time_work, while batt_presence_work can requeue itself. rt9455_remove() cancels max_charging_time_work before batt_presence_work. The latter can therefore queue max_charging_time_work after it has already been cancelled: rt9455_remove() workqueue cancel pwr_rdy_work cancel max_charging_time_work batt_presence_work queues max_charging_time_work cancel batt_presence_work return devres frees rt9455_info max_charging_time_work dereferences rt9455_info The IRQ also remains registered until devres cleanup and can queue more work after any of the cancellation calls. If rt9455_hw_init() fails after the IRQ has been requested, probe returns without cancelling work that may already have been queued. A pending callback can then access rt9455_info after it has been freed. Register rt9455_cancel_all_delayed_works() through devm_add_action_or_reset() right after devm_power_supply_register(). devres invokes the action in reverse registration order, after the managed IRQ has been freed and before rt9455_info is released, so the delayed works are drained in both rt9455_remove() and the probe error path. Cancel pwr_rdy_work and batt_presence_work before max_charging_time_work because both can queue the latter. This issue was found by an in-house static analysis tool.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | >=e86d69dd786e94046b8f5be7df1b9a8226a40b2a <df67c7a2fff8414aa766b8cd5ffe11ec1ca27d02, >=e86d69dd786e94046b8f5be7df1b9a8226a40b2a <1b9978433c61a9b46e48832a1ebceee1cf5c9eb4, >=e86d69dd786e94046b8f5be7df1b9a8226a40b2a <3def4721431f3e374e1e3124f4d32bb07ae8df1c, >=e86d69dd786e94046b8f5be7df1b9a8226a40b2a <3e7a1ebc32fad5a558254a478efd401c17a24381, >=e86d69dd786e94046b8f5be7df1b9a8226a40b2a <442c60c08ec23ac45da0a58877cab05e0a58f4ea, >=e86d69dd786e94046b8f5be7df1b9a8226a40b2a <7323e562f6961e4b7bce3225cde4ecbc78260deb, >=e86d69dd786e94046b8f5be7df1b9a8226a40b2a <c09a2e4f8f101a44bd786a31696c958473469be0, >=e86d69dd786e94046b8f5be7df1b9a8226a40b2a <c8645073876cbb1cdc8c2b995d093d08facfb187, =4.2 | df67c7a2fff8414aa766b8cd5ffe11ec1ca27d02, 1b9978433c61a9b46e48832a1ebceee1cf5c9eb4, 3def4721431f3e374e1e3124f4d32bb07ae8df1c, 3e7a1ebc32fad5a558254a478efd401c17a24381, 442c60c08ec23ac45da0a58877cab05e0a58f4ea, 7323e562f6961e4b7bce3225cde4ecbc78260deb, c09a2e4f8f101a44bd786a31696c958473469be0, c8645073876cbb1cdc8c2b995d093d08facfb187 |
| linux-kernel: Kernel | >=5.11.0 <5.15.224, >=5.16.0 <6.1.191, >=6.13.0 <6.18.50, >=6.19.0 <7.2.4, >=6.2.0 <6.6.157, >=6.7.0 <6.12.109, >=4.2.0 <5.10.273 | 5.15.224, 6.1.191, 6.18.50, 7.2.4, 6.6.157, 6.12.109, 5.10.273 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket