CVE-2026-45946

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

HIGH
7.8
CVSS Score
Published: May 27, 2026 at 12:18 PM UTC
Updated: June 17, 2026 at 10:52 AM 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
HIGH7.8
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: power: supply: ab8500: 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()`. Commit 1c1f13a006ed ("power: supply: ab8500: Move to componentized binding") introduced this issue during a refactorization. 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.

v ≥ 5.13.45.13.4 ≤ v < 5.145.13.4 ≤ v < 5.15.2025.14 ≤ v < 5.15.2025.14 ≤ v < 6.1.1655.14 ≤ v < 6.12.755.14 ≤ v < 6.18.145.14 ≤ v < 6.19.45.14 ≤ v < 6.6.1285.14 ≤ v < 7.05.16 ≤ v < 6.1.1656.13 ≤ v < 6.18.146.19 ≤ v < 6.19.46.2 ≤ v < 6.6.1286.7 ≤ v < 6.12.751c1f13a006ed0d71bb5664c8b7e3e77a28da3beb341db343768bc44f3512facc464021730d64071c5.13.45.14
Vendor states this is fixed in 43cbb78ee047b9b12d096d40e3be265969d4c1f8 (fixed)
Vendor states this is fixed in 46dbda27b028d78087667e8280966b99cec015ca (fixed)
Vendor states this is fixed in 551672981fe227122258a25a385a05f5c0746ad6 (fixed)
Vendor states this is fixed in 709db4b476e254579d9c48ec34d397a41ca0c407 (fixed)
Vendor states this is fixed in 847eeb6c0efcd76c7def73857cf798a4fcd8f79b (fixed)
Vendor states this is fixed in c4af8a98bb52825a5331ae1d0604c0ea6956ba4b (fixed)
Vendor states this is fixed in f50433f2603def08b21a4bf2fd238687fb5cbde9 (fixed)
Vendor states this is fixed in 5.14 (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

Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
HIGH
Integrity
HIGH
Availability
HIGH
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