PoC Monitor
← All CVEs
CVE-2026-89465published 11 Sep 2026 19:43 UTCData: JSON · API

Linux

power: supply: rt9455: quiesce delayed work before teardown

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.

First public PoC None yetno public PoC found
Public PoCs00 on GitHub
CVSS8.4high · scored by CNA
CISA KEV Not listednot known exploited

Affected versions and mitigation

From the CVE record and the vendor's references.

Affected

Linux Linux
  • >= e86d69dd786e94046b8f5be7df1b9a8226a40b2a, < 3def4721431f3e374e1e3124f4d32bb07ae8df1c
  • >= e86d69dd786e94046b8f5be7df1b9a8226a40b2a, < c8645073876cbb1cdc8c2b995d093d08facfb187
  • >= e86d69dd786e94046b8f5be7df1b9a8226a40b2a, < c09a2e4f8f101a44bd786a31696c958473469be0
  • >= e86d69dd786e94046b8f5be7df1b9a8226a40b2a, < 442c60c08ec23ac45da0a58877cab05e0a58f4ea
  • >= e86d69dd786e94046b8f5be7df1b9a8226a40b2a, < df67c7a2fff8414aa766b8cd5ffe11ec1ca27d02
  • >= e86d69dd786e94046b8f5be7df1b9a8226a40b2a, < 1b9978433c61a9b46e48832a1ebceee1cf5c9eb4
  • >= e86d69dd786e94046b8f5be7df1b9a8226a40b2a, < 7323e562f6961e4b7bce3225cde4ecbc78260deb
  • >= e86d69dd786e94046b8f5be7df1b9a8226a40b2a, < 3e7a1ebc32fad5a558254a478efd401c17a24381

Fixed in 3def4721431f3e374e1e3124f4d32bb07ae8df1c, c8645073876cbb1cdc8c2b995d093d08facfb187, c09a2e4f8f101a44bd786a31696c958473469be0, 442c60c08ec23ac45da0a58877cab05e0a58f4ea, df67c7a2fff8414aa766b8cd5ffe11ec1ca27d02, 1b9978433c61a9b46e48832a1ebceee1cf5c9eb4, 7323e562f6961e4b7bce3225cde4ecbc78260deb, 3e7a1ebc32fad5a558254a478efd401c17a24381

Linux Linux
  • 4.2

Fixed in 0, 5.10.273, 5.15.224, 6.1.191, 6.6.157, 6.12.109, 6.18.50, 7.2.4, 7.3

Mitigation

Upgrade Linux to 3def4721431f3e374e1e3124f4d32bb07ae8df1c or c8645073876cbb1cdc8c2b995d093d08facfb187 or c09a2e4f8f101a44bd786a31696c958473469be0 or 442c60c08ec23ac45da0a58877cab05e0a58f4ea or df67c7a2fff8414aa766b8cd5ffe11ec1ca27d02 or 1b9978433c61a9b46e48832a1ebceee1cf5c9eb4 or 7323e562f6961e4b7bce3225cde4ecbc78260deb or 3e7a1ebc32fad5a558254a478efd401c17a24381 or later.

Upgrade Linux to 0 or 5.10.273 or 5.15.224 or 6.1.191 or 6.6.157 or 6.12.109 or 6.18.50 or 7.2.4 or 7.3 or later.

Timeline

Days relative to CVE publication
-2t=0+2+4+6+8CVE published11 Sep 2026 · t = 0

No public PoC found yet; not in CISA KEV.

PoC repositories

Found on GitHub.

No PoC repositories found yet.