CVE-2026-45867

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

HIGH
7.8
CVSS Score
Published: May 27, 2026 at 12:15 PM UTC
Updated: June 27, 2026 at 11:41 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: act8945a: 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.9 ≤ v < 5.10.2524.9 ≤ v < 5.15.2024.9 ≤ v < 6.1.1654.9 ≤ v < 6.12.754.9 ≤ v < 6.18.144.9 ≤ v < 6.19.44.9 ≤ v < 6.6.1284.9 ≤ 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.9a09209acd6a808794bdd7866af3678d1fd1d90e7
Vendor states this is fixed in 0768e8525a46df103647ca5059b32320d7fd17e4 (fixed)
Vendor states this is fixed in 3291c51d4684d048dd2eb91b5b65fcfdaf72141f (fixed)
Vendor states this is fixed in 697bb5dc0cb4791e244f3970b067bc1ef33be9d9 (fixed)
Vendor states this is fixed in 76a42ba547a9b2e2337894f67a4d9247445007d5 (fixed)
Vendor states this is fixed in 83c1bd466c514cb24ca6ef347c5aac76a13c4e1e (fixed)
Vendor states this is fixed in d023ef9f748b2090f7a9dbdd5c622b6ad99088ea (fixed)
Vendor states this is fixed in f27eb76def5c07e4d7cc468b40741f19dafc83ce (fixed)
Vendor states this is fixed in f2a0777b1e5a3cee1712c4d3e9095c0df8fc8cb3 (fixed)
Vendor states this is fixed in 4.9 (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

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