CVE-2026-45936

power: supply: goldfish: 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.1%

Description

In the Linux kernel, the following vulnerability has been resolved: power: supply: goldfish: 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.

3.9 ≤ v < 5.10.2523.9 ≤ v < 5.15.2023.9 ≤ v < 6.1.1653.9 ≤ v < 6.12.753.9 ≤ v < 6.18.143.9 ≤ v < 6.19.43.9 ≤ v < 6.6.1283.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.753.984d7b768748943db2bb658b43931fdab04c224cc
Vendor states this is fixed in 0b29ffe4090a3fc7a7649de20e1eb1e53adddac7 (fixed)
Vendor states this is fixed in 33751e28842bf5aee5ef7b2b8d5e456a069095cb (fixed)
Vendor states this is fixed in 4350505e82b4f972ddb788e1c712c557c38859d0 (fixed)
Vendor states this is fixed in 589d4fe56713c6344cd9f8939f9c7621c85f0966 (fixed)
Vendor states this is fixed in 77ea437faa4c06362e3ecfd2d7264eaa7ac1e82c (fixed)
Vendor states this is fixed in 8c89aade8335e26a6a7dcda18992d15f51943927 (fixed)
Vendor states this is fixed in b2ce982e2e0c888dc55c888ad0e20ea04daf2e6b (fixed)
Vendor states this is fixed in bad8b61eb5059acd88349680e47839342dc89e94 (fixed)
Vendor states this is fixed in 3.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

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