CVE-2026-45902 Details
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.
A use-after-free vulnerability has been identified in the Linux kernel's BQ256XX charger driver, specifically within the power supply management. 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 properly unregistered, creating a race condition. During the removal process, an interrupt can be triggered after the power supply handle has been freed but before the IRQ handler has been unregistered. This leads to the IRQ handler invoking 'power_supply_changed()' with a freed handle, which typically causes a system crash or silently corrupts memory. A similar problem can occur during the probe phase, where an interrupt might fire before the power supply handle is registered, resulting in the handle being used uninitialized. The vulnerability affects several versions of the Linux kernel.
The vulnerability has been addressed by modifying the driver to request the IRQ after the power supply handle has been registered, ensuring that the handle is not freed before the interrupt handler is unregistered.
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/4b6fb0b6124f558131e502e3ffd03e6583b3ace6 | kernel.org | Patch |
| https://git.kernel.org/stable/c/74b5a88318db97d51bb40f774736553c2acd1514 | kernel.org | Patch |
| https://git.kernel.org/stable/c/8005843369723d9c8975b7c4202d1b85d6125302 | kernel.org | Patch |
| https://git.kernel.org/stable/c/81d3688c9a2158329391e08f2d0b8ba204216044 | kernel.org | Patch |
| https://git.kernel.org/stable/c/83c27fdd696ac13d023ef7a0345301be93209c53 | kernel.org | Patch |
| https://git.kernel.org/stable/c/8796910131a32ff29275052df768ef022929a394 | kernel.org | Patch |
| https://git.kernel.org/stable/c/cb5c743936edcebc51880eeb6bf04979b5c9438b | kernel.org | Patch |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-416 | Use After Free | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| linux linux kernel | >= 5.12, < 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 |