Skip to main content
VulnerabilityPublished Updated

CVE-2026-89465: Linux kernel · power: supply: rt9455: quiesce delayed work before teardown

Affects Linux kernelSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.4 High · fixed in df67c7a2fff8414aa766b8cd5ffe11ec1ca27d02 : patch Linux kernel soon.

Data as of 30 Oct 2026, 12:49 UTC

CVSS 3.1 base score
8.4High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (Linux)CVSS 3.18.4
Patch
Available – fixed in df67c7a2fff8414aa766b8cd5ffe11ec1ca27d02, c8645073876cbb1cdc8c2b995d093d08facfb187, c09a2e4f8f101a44bd786a31696c958473469be0 +5
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 11 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ e86d69dd786e94046b8f5be7df1b9a8226a40b2a, < df67c7a2fff8414aa766b8cd5ffe11ec1ca27d02
Fixed in
  • df67c7a2fff8414aa766b8cd5ffe11ec1ca27d02
LinuxLinuxAffected
  • ≥ e86d69dd786e94046b8f5be7df1b9a8226a40b2a, < c8645073876cbb1cdc8c2b995d093d08facfb187
Fixed in
  • c8645073876cbb1cdc8c2b995d093d08facfb187
LinuxLinuxAffected
  • ≥ e86d69dd786e94046b8f5be7df1b9a8226a40b2a, < c09a2e4f8f101a44bd786a31696c958473469be0
Fixed in
  • c09a2e4f8f101a44bd786a31696c958473469be0
LinuxLinuxAffected
  • ≥ e86d69dd786e94046b8f5be7df1b9a8226a40b2a, < 7323e562f6961e4b7bce3225cde4ecbc78260deb
Fixed in
  • 7323e562f6961e4b7bce3225cde4ecbc78260deb
LinuxLinuxAffected
  • ≥ e86d69dd786e94046b8f5be7df1b9a8226a40b2a, < 442c60c08ec23ac45da0a58877cab05e0a58f4ea
Fixed in
  • 442c60c08ec23ac45da0a58877cab05e0a58f4ea
LinuxLinuxAffected
  • ≥ e86d69dd786e94046b8f5be7df1b9a8226a40b2a, < 3e7a1ebc32fad5a558254a478efd401c17a24381
Fixed in
  • 3e7a1ebc32fad5a558254a478efd401c17a24381

Description

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.

References

Community reviews

Loading reviews…