CVE-2026-45902

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

HIGH
7.8
CVSS Score
Published: May 27, 2026 at 12:17 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: bq256xx: 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.

5.12 ≤ v < 5.15.2025.12 ≤ v < 6.1.1655.12 ≤ v < 6.12.755.12 ≤ v < 6.18.145.12 ≤ v < 6.19.45.12 ≤ v < 6.6.1285.12 ≤ 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.7532e4978bb920d047fe5de3ea42d176f267c01f635.12
Vendor states this is fixed in 4b6fb0b6124f558131e502e3ffd03e6583b3ace6 (fixed)
Vendor states this is fixed in 74b5a88318db97d51bb40f774736553c2acd1514 (fixed)
Vendor states this is fixed in 8005843369723d9c8975b7c4202d1b85d6125302 (fixed)
Vendor states this is fixed in 81d3688c9a2158329391e08f2d0b8ba204216044 (fixed)
Vendor states this is fixed in 83c27fdd696ac13d023ef7a0345301be93209c53 (fixed)
Vendor states this is fixed in 8796910131a32ff29275052df768ef022929a394 (fixed)
Vendor states this is fixed in cb5c743936edcebc51880eeb6bf04979b5c9438b (fixed)
Vendor states this is fixed in 5.12 (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

StatusUNDERGOING ANALYSIS
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