Answer in brief
CVE-2026-45902 records a High severity (CVSS 7.8) vulnerability in power: supply: bq256xx: Fix use-after-free in power_supply_changed(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2026-45902 records a High severity (CVSS 7.8) vulnerability in power: supply: bq256xx: Fix use-after-free in power_supply_changed(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=32e4978bb920d047fe5de3ea42d176f267c01f63 <81d3688c9a2158329391e08f2d0b8ba204216044 || >=32e4978bb920d047fe5de3ea42d176f267c01f63 <74b5a88318db97d51bb40f774736553c2acd1514 || >=32e4978bb920d047fe5de3ea42d176f267c01f63 <cb5c743936edcebc51880eeb6bf04979b5c9438b || >=32e4978bb920d047fe5de3ea42d176f267c01f63 <83c27fdd696ac13d023ef7a0345301be93209c53 || >=32e4978bb920d047fe5de3ea42d176f267c01f63 <4b6fb0b6124f558131e502e3ffd03e6583b3ace6 || >=32e4978bb920d047fe5de3ea42d176f267c01f63 <8796910131a32ff29275052df768ef022929a394 || >=32e4978bb920d047fe5de3ea42d176f267c01f63 <8005843369723d9c8975b7c4202d1b85d6125302 | 81d3688c9a2158329391e08f2d0b8ba204216044, 74b5a88318db97d51bb40f774736553c2acd1514, cb5c743936edcebc51880eeb6bf04979b5c9438b, 83c27fdd696ac13d023ef7a0345301be93209c53, 4b6fb0b6124f558131e502e3ffd03e6583b3ace6, 8796910131a32ff29275052df768ef022929a394, 8005843369723d9c8975b7c4202d1b85d6125302 |
| Linux/Linuxgeneric | 5.12 | Not reported |
Published upstream
May 27, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Jun 24, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jun 24, 2026
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.
Quoted source text, attributed separately from HOL analysis.
CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=32e4978bb920d047fe5de3ea42d176f267c01f63 <81d3688c9a2158329391e08f2d0b8ba204216044 || >=32e4978bb920d047fe5de3ea42d176f267c01f63 <74b5a88318db97d51bb40f774736553c2acd1514 || >=32e4978bb920d047fe5de3ea42d176f267c01f63 <cb5c743936edcebc51880eeb6bf04979b5c9438b || >=32e4978bb920d047fe5de3ea42d176f267c01f63 <83c27fdd696ac13d023ef7a0345301be93209c53 || >=32e4978bb920d047fe5de3ea42d176f267c01f63 <4b6fb0b6124f558131e502e3ffd03e6583b3ace6 || >=32e4978bb920d047fe5de3ea42d176f267c01f63 <8796910131a32ff29275052df768ef022929a394 || >=32e4978bb920d047fe5de3ea42d176f267c01f63 <8005843369723d9c8975b7c4202d1b85d6125302 | 81d3688c9a2158329391e08f2d0b8ba204216044, 74b5a88318db97d51bb40f774736553c2acd1514, cb5c743936edcebc51880eeb6bf04979b5c9438b, 83c27fdd696ac13d023ef7a0345301be93209c53, 4b6fb0b6124f558131e502e3ffd03e6583b3ace6, 8796910131a32ff29275052df768ef022929a394, 8005843369723d9c8975b7c4202d1b85d6125302 |
| Linux/Linuxgeneric | 5.12 | Not reported |
Published upstream
May 27, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Jun 24, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jun 24, 2026
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.
Quoted source text, attributed separately from HOL analysis.