CVE-2026-45885

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

HIGH
7.8
CVSS Score
Published: May 27, 2026 at 12:16 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: cpcap-battery: 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.13 ≤ v < 5.10.2524.13 ≤ v < 5.15.2024.13 ≤ v < 6.1.1654.13 ≤ v < 6.12.754.13 ≤ v < 6.18.144.13 ≤ v < 6.19.44.13 ≤ v < 6.6.1284.13 ≤ 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.13874b2adbed1253a11549cb9b7b912ab65fea9cf2
Vendor states this is fixed in 2841bbb5a35c4449c0a0458e8e476b2a62f95147 (fixed)
Vendor states this is fixed in 2ce2334be155bd8bad6377e99984246ce4dbd08c (fixed)
Vendor states this is fixed in 3ff75cba1c98349a23a8f9333981deba1972cc11 (fixed)
Vendor states this is fixed in 642f33e34b969eedec334738fd5df95d2dc42742 (fixed)
Vendor states this is fixed in c549dd3de4b3f6e726d1b8386d40ccf7d3abdbe4 (fixed)
Vendor states this is fixed in cbb9b07f88a9ef6518934c41eb3e8cf840d657d5 (fixed)
Vendor states this is fixed in e261be6f18929f2397cd54cd583a2df624c129c1 (fixed)
Vendor states this is fixed in f3fbe309c9bfe1aac1e2b26543e9dc4829f3275a (fixed)
Vendor states this is fixed in 4.13 (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