CVE-2026-45936 Details
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.
A use-after-free vulnerability has been identified in the Linux kernel's goldfish power supply driver. This issue arises because the 'devm_' variant for requesting interrupts is used before the 'devm_' variant for registering the power supply handle. As a result, the power supply handle is deallocated before the interrupt handler is unregistered, creating a race condition. An interrupt can be triggered after the handle has been freed but before the IRQ handler unregistration is completed. This leads to the IRQ handler calling 'power_supply_changed()' with a freed handle, causing system crashes or memory corruption. A similar issue can occur during the 'probe()' phase, where an interrupt might fire before the power supply handle is fully initialized, also leading to the use of an uninitialized handle in 'power_supply_changed()'.
The vulnerability has been addressed by modifying the driver to request the interrupt after the power supply handle has been registered. Users should update to the latest version of the Linux kernel where this fix has been applied.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
No SSVC data is available for this CVE.
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://git.kernel.org/stable/c/0b29ffe4090a3fc7a7649de20e1eb1e53adddac7 | kernel.org | Patch |
| https://git.kernel.org/stable/c/33751e28842bf5aee5ef7b2b8d5e456a069095cb | kernel.org | Patch |
| https://git.kernel.org/stable/c/4350505e82b4f972ddb788e1c712c557c38859d0 | kernel.org | Patch |
| https://git.kernel.org/stable/c/589d4fe56713c6344cd9f8939f9c7621c85f0966 | kernel.org | Patch |
| https://git.kernel.org/stable/c/77ea437faa4c06362e3ecfd2d7264eaa7ac1e82c | kernel.org | Patch |
| https://git.kernel.org/stable/c/8c89aade8335e26a6a7dcda18992d15f51943927 | kernel.org | Patch |
| https://git.kernel.org/stable/c/b2ce982e2e0c888dc55c888ad0e20ea04daf2e6b | kernel.org | Patch |
| https://git.kernel.org/stable/c/bad8b61eb5059acd88349680e47839342dc89e94 | kernel.org | Patch |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-416 | Use After Free | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| linux linux kernel | >= 3.9, < 5.10.252 >= 5.11, < 5.15.202 >= 5.16, < 6.1.165 >= 6.2, < 6.6.128 >= 6.7, < 6.12.75 >= 6.13, < 6.18.14 >= 6.19, < 6.19.4 |
CPE
Remediation
| |
Change History
3 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 24, 2026 | Initial Analysis | [email protected] |
| Jun 17, 2026 | CVE Modified | kernel.org |
| May 27, 2026 | New CVE Received | kernel.org |