CVE-2026-46270

power: supply: rt9455: Fix use-after-free in power_supply_changed()

HIGH
8.4
CVSS Score
Published: June 3, 2026 at 03:50 PM UTC
Updated: August 5, 2026 at 01:24 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH8.4
Exploit prediction
EPSS 0.1%

Description

In the Linux kernel, the following vulnerability has been resolved: power: supply: rt9455: Fix use-after-free in power_supply_changed() Using the `devm_` variant for requesting IRQ _before_ the `devm_` variant for allocating/registering the `power_supply` handle, means that the `power_supply` handle will be deallocated/unregistered _before_ the interrupt handler (since `devm_` naturally deallocates in reverse allocation order). This means that during removal, there is a race condition where an interrupt can fire just _after_ the `power_supply` handle has been freed, *but* just _before_ the corresponding unregistration of the IRQ handler has run. This will lead to the IRQ handler calling `power_supply_changed()` with a freed `power_supply` handle. Which usually crashes the system or otherwise silently corrupts the memory... Note that there is a similar situation which can also happen during `probe()`; the possibility of an interrupt firing _before_ registering the `power_supply` handle. This would then lead to the nasty situation of using the `power_supply` handle *uninitialized* in `power_supply_changed()`. Fix this racy use-after-free by making sure the IRQ is requested _after_ the registration of the `power_supply` handle.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

4.2 ≤ v < 5.10.2524.2 ≤ v < 5.15.2024.2 ≤ v < 6.1.1654.2 ≤ v < 6.12.754.2 ≤ v < 6.18.144.2 ≤ v < 6.19.44.2 ≤ v < 6.6.1284.2 ≤ v < 7.05.11 ≤ v < 5.15.2025.16 ≤ v < 6.1.1656.13 ≤ v < 6.18.146.19 ≤ v < 6.19.46.2 ≤ v < 6.6.1286.7 ≤ v < 6.12.754.2e86d69dd786e94046b8f5be7df1b9a8226a40b2a
Vendor states this is fixed in 2178dc65d45e2f7bcaa8af8d80d100419bdab251 (fixed)
Vendor states this is fixed in 62d753b916bd500bb269b7078cdab73198ab4718 (fixed)
Vendor states this is fixed in 64e15155095f39f4dec9b4659da1238ef8fc54d4 (fixed)
Vendor states this is fixed in 721449a15170fc5f028a7576d7f65b9f60d53482 (fixed)
Vendor states this is fixed in a39f8f06216f73ef40e71e2fe4ad071964c1fd36 (fixed)
Vendor states this is fixed in af261f218a7606f93d2c786353d60bb4feb56ef0 (fixed)
Vendor states this is fixed in d4e2e3c3caa26b93aa9f36d0a6824b584e2a8dfc (fixed)
Vendor states this is fixed in e2febe375e5ea5afed92f4cd9711bde8f24ee6d2 (fixed)
Vendor states this is fixed in 4.2 (unaffected)
Vendor states this is fixed in 5.10.252 (unaffected)
Vendor states this is fixed in 5.15.202 (unaffected)
Vendor states this is fixed in 6.1.165 (unaffected)
Vendor states this is fixed in 6.12.75 (unaffected)
Vendor states this is fixed in 6.18.14 (unaffected)
Vendor states this is fixed in 6.19.4 (unaffected)
Vendor states this is fixed in 6.6.128 (unaffected)
Vendor states this is fixed in 7.0 (unaffected)

CVSS

8.4HIGHLinux
Vector?

Quick Info

StatusANALYZED
CWE
CWE-416

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card