CVE-2026-45902
Awaiting Analysis Awaiting Analysis - Queue
Use-After-Free in Linux Kernel BQ256XX Power Supply Driver

Publication date: 2026-05-27

Last updated on: 2026-05-27

Assigner: kernel.org

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.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-05-27
Last Modified
2026-05-27
Generated
2026-06-16
AI Q&A
2026-05-27
EPSS Evaluated
2026-06-15
NVD
CVE-2026-45902
EUVD
EUVD-2026-32368
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
ti power_supply *
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Executive Summary

This vulnerability is a use-after-free bug in the Linux kernel's power supply driver for bq256xx devices. It occurs because the interrupt request (IRQ) is requested before the power_supply handle is allocated and registered. Since the system deallocates resources in reverse order, the power_supply handle can be freed before the IRQ handler is unregistered during device removal.

As a result, an interrupt can trigger just after the power_supply handle has been freed but before the IRQ handler is unregistered. This causes the IRQ handler to call power_supply_changed() with a freed (invalid) power_supply handle, which usually crashes the system or corrupts memory silently.

A similar issue can happen during device probe, where an interrupt fires before the power_supply handle is registered, leading to the use of an uninitialized handle.

The fix involves ensuring that the IRQ is requested only after the power_supply handle has been registered, preventing the race condition.

Impact Analysis

This vulnerability can cause system crashes or silent memory corruption due to the use of freed or uninitialized power_supply handles in interrupt handlers.

Such crashes can lead to system instability, data loss, or unexpected behavior in devices using the affected Linux kernel power supply driver.

Mitigation Strategies

The vulnerability is caused by a race condition in the Linux kernel power supply driver bq256xx, where an interrupt handler may access a freed or uninitialized power_supply handle, leading to crashes or memory corruption.

To mitigate this vulnerability, ensure that your Linux kernel is updated to a version where this issue is fixed. The fix involves requesting the IRQ only after the power_supply handle has been registered, preventing the use-after-free condition.

If updating the kernel immediately is not possible, consider disabling or unloading the affected power supply driver (bq256xx) to prevent the race condition from occurring.

Compliance Impact

The provided information does not include any details about the impact of this vulnerability on compliance with common standards and regulations such as GDPR or HIPAA.

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-45902. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart