---
id: CVE-2026-89465
title: 'power: supply: rt9455: quiesce delayed work before teardown'
summary: |-
  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_wo…
severity: high
cvss: 8.4
cvssVector: 'CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H'
cvssSource: cna
cwe:
  - CWE-825
vendor: Linux
product: Linux
affected:
  - >-
    Linux >= e86d69dd786e94046b8f5be7df1b9a8226a40b2a <
    442c60c08ec23ac45da0a58877cab05e0a58f4ea
  - >-
    Linux >= e86d69dd786e94046b8f5be7df1b9a8226a40b2a <
    df67c7a2fff8414aa766b8cd5ffe11ec1ca27d02
  - >-
    Linux >= e86d69dd786e94046b8f5be7df1b9a8226a40b2a <
    1b9978433c61a9b46e48832a1ebceee1cf5c9eb4
  - >-
    Linux >= e86d69dd786e94046b8f5be7df1b9a8226a40b2a <
    7323e562f6961e4b7bce3225cde4ecbc78260deb
  - >-
    Linux >= e86d69dd786e94046b8f5be7df1b9a8226a40b2a <
    3e7a1ebc32fad5a558254a478efd401c17a24381
  - Linux 4.2
published: '2026-09-11'
updated: '2026-10-19'
sourceUpdated: '2026-10-19T08:47:14.457Z'
source: CVEORG
sourceUrl: 'https://www.cve.org/CVERecord?id=CVE-2026-89465'
references:
  - url: 'https://git.kernel.org/stable/c/442c60c08ec23ac45da0a58877cab05e0a58f4ea'
  - url: 'https://git.kernel.org/stable/c/df67c7a2fff8414aa766b8cd5ffe11ec1ca27d02'
  - url: 'https://git.kernel.org/stable/c/1b9978433c61a9b46e48832a1ebceee1cf5c9eb4'
  - url: 'https://git.kernel.org/stable/c/7323e562f6961e4b7bce3225cde4ecbc78260deb'
  - url: 'https://git.kernel.org/stable/c/3e7a1ebc32fad5a558254a478efd401c17a24381'
  - url: >-
      https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-89465.json
  - url: 'https://access.redhat.com/security/cve/CVE-2026-89465'
  - url: 'https://bugzilla.redhat.com/show_bug.cgi?id=2532410'
  - url: 'https://www.cve.org/CVERecord?id=CVE-2026-89465'
  - url: 'https://nvd.nist.gov/vuln/detail/CVE-2026-89465'
  - url: >-
      https://git.kernel.org/pub/scm/linux/security/vulns.git/plain/cve/published/2026/CVE-2026-89465.mbox
tags:
  - cve.org
  - csaf
  - vex
  - red-hat
  - score-dispute
epss: 0.00142
epssPercentile: 0.0345
scores:
  cna: 8.4
  vendor: 5.5
ingestedAt: '2026-09-14T15:23:07.453Z'
---

## Overview

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

- `Linux >= e86d69dd786e94046b8f5be7df1b9a8226a40b2a < 442c60c08ec23ac45da0a58877cab05e0a58f4ea`
- `Linux >= e86d69dd786e94046b8f5be7df1b9a8226a40b2a < df67c7a2fff8414aa766b8cd5ffe11ec1ca27d02`
- `Linux >= e86d69dd786e94046b8f5be7df1b9a8226a40b2a < 1b9978433c61a9b46e48832a1ebceee1cf5c9eb4`
- `Linux >= e86d69dd786e94046b8f5be7df1b9a8226a40b2a < 7323e562f6961e4b7bce3225cde4ecbc78260deb`
- `Linux >= e86d69dd786e94046b8f5be7df1b9a8226a40b2a < 3e7a1ebc32fad5a558254a478efd401c17a24381`
- `Linux 4.2`

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.

## Vendor advisories

- **Red Hat VEX** · Moderate · updated 2026-09-17 · [vex](https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-89465.json)