Answer in brief
CVE-2026-89463 records a Unknown severity vulnerability in power: supply: ucs1002: 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). 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). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=81196e2e57fc5b88f6b8ca98372a3dde047aa49d <4ca2a4678202f15eb790eb7f1d562061709caea7 || >=81196e2e57fc5b88f6b8ca98372a3dde047aa49d <39b60d615dfa1725c235351fb12bc72e5f8a8d32 || >=81196e2e57fc5b88f6b8ca98372a3dde047aa49d <35242c93d35f391afdc84cef6236b8ad57f1df24 || >=81196e2e57fc5b88f6b8ca98372a3dde047aa49d <609af0ceeaefdfa42cd01dd060b20f2e41f9a232 | 4ca2a4678202f15eb790eb7f1d562061709caea7, 39b60d615dfa1725c235351fb12bc72e5f8a8d32, 35242c93d35f391afdc84cef6236b8ad57f1df24, 609af0ceeaefdfa42cd01dd060b20f2e41f9a232 |
| Linux/Linuxgeneric | 5.10 | Not reported |
Published upstream
Sep 11, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 11, 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: ucs1002: fix use-after-free on remove ucs1002 has no remove callback, so unbind runs entirely through devm. The alert IRQ handler queues the health_poll delayed work, and the work reschedules itself while the chip reports a bad-health condition. devm frees the alert IRQ, which only synchronizes the handler; it does not cancel the delayed work, which can then run after devm frees the driver data and dereference it. Register health_poll with devm_delayed_work_autocancel() before the alert IRQ is requested. devm then frees the IRQ before cancelling the work, so the handler can no longer queue it and the work is cancelled before the driver data is freed. This issue was found by an in-house static analysis tool.
Quoted source text, attributed separately from HOL analysis.