Answer in brief
CVE-2026-89475 records a Unknown severity vulnerability in power: supply: bq24257: fix use-after-free on remove. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), 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.
A CVSS score is not reported in the current record. 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), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=2219a935963e5eeb19e5abfb99475fcc06bbb804 <861ec73ce86e2ca18082cc7be4f140a5bbdf1428 || >=2219a935963e5eeb19e5abfb99475fcc06bbb804 <f495808cdd6d9576965787cf6d9737d0b0e86b73 || >=2219a935963e5eeb19e5abfb99475fcc06bbb804 <47ccbad210f48721c30d69d65b83dc9fff919ca9 || >=2219a935963e5eeb19e5abfb99475fcc06bbb804 <9d34c9d660c3d0931d2cc749c46c47cf31f96e48 | 861ec73ce86e2ca18082cc7be4f140a5bbdf1428, f495808cdd6d9576965787cf6d9737d0b0e86b73, 47ccbad210f48721c30d69d65b83dc9fff919ca9, 9d34c9d660c3d0931d2cc749c46c47cf31f96e48 |
| Linux/Linuxgeneric | 4.2 | Not reported |
| Linux/Linuxgeneric | >=2219a935963e5eeb19e5abfb99475fcc06bbb804 <9d77fd7dd9a3ad57f7655c5264b503b85adbb7b8 || >=2219a935963e5eeb19e5abfb99475fcc06bbb804 <a279e64c907f5638bb34cb8e2c9285798cf5f690 || >=2219a935963e5eeb19e5abfb99475fcc06bbb804 <6d2eb93975c07b0169a3287efc1ae3b60cf52d8e || >=2219a935963e5eeb19e5abfb99475fcc06bbb804 <861ec73ce86e2ca18082cc7be4f140a5bbdf1428 || >=2219a935963e5eeb19e5abfb99475fcc06bbb804 <f495808cdd6d9576965787cf6d9737d0b0e86b73 || >=2219a935963e5eeb19e5abfb99475fcc06bbb804 <47ccbad210f48721c30d69d65b83dc9fff919ca9 || >=2219a935963e5eeb19e5abfb99475fcc06bbb804 <9d34c9d660c3d0931d2cc749c46c47cf31f96e48 | 9d77fd7dd9a3ad57f7655c5264b503b85adbb7b8, a279e64c907f5638bb34cb8e2c9285798cf5f690, 6d2eb93975c07b0169a3287efc1ae3b60cf52d8e, 861ec73ce86e2ca18082cc7be4f140a5bbdf1428, f495808cdd6d9576965787cf6d9737d0b0e86b73, 47ccbad210f48721c30d69d65b83dc9fff919ca9, 9d34c9d660c3d0931d2cc749c46c47cf31f96e48 |
Published upstream
Sep 11, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 11, 2026
In the Linux kernel, the following vulnerability has been resolved: power: supply: bq24257: fix use-after-free on remove The STAT-pin interrupt is devm-managed, so it stays armed until the devm cleanup that runs after remove() returns. remove() cancels bq->iilimit_setup_work while the threaded handler can still fire; that handler reschedules the work and dereferences bq, so the work runs against freed memory once devm frees bq. Make the delayed work device-managed with devm_delayed_work_autocancel(), registered before the interrupt request. The devm cleanup then releases the interrupt first, so the handler can no longer reschedule the work, and cancels the work before bq is freed. The explicit cancel_delayed_work_sync() in remove() is no longer needed and is dropped. Found by static analysis.
Quoted source text, attributed separately from HOL analysis.