Answer in brief
CVE-2026-89464 records a Unknown severity vulnerability in power: supply: twl4030_charger: cancel workers via devm. 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 | >=d6ccc442b12102414c1343f0adacaa8a1aaa516c <72a2d6cd049f892853e4e2d8d8fc5e7d0244a458 || >=d6ccc442b12102414c1343f0adacaa8a1aaa516c <a4460e89d4088cfec2da5be33e265ef1a8e780e9 || >=d6ccc442b12102414c1343f0adacaa8a1aaa516c <b955da82db4170bdf1c784dc457287aa0c977378 || >=d6ccc442b12102414c1343f0adacaa8a1aaa516c <6eba34732524067da2aad5ddfdfbc641ded10e9e | 72a2d6cd049f892853e4e2d8d8fc5e7d0244a458, a4460e89d4088cfec2da5be33e265ef1a8e780e9, b955da82db4170bdf1c784dc457287aa0c977378, 6eba34732524067da2aad5ddfdfbc641ded10e9e |
| Linux/Linuxgeneric | 2.6.39 | 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: twl4030_charger: cancel workers via devm bci is devm-allocated. Two workers (bci->work and bci->current_worker) dereference it. twl4030_bci_remove() disables charging and masks interrupts. It cancels neither worker. A worker pending at remove() can run after devm frees bci. The USB transceiver comes from devm_usb_get_phy_by_node(). devm unregisters its notifier only after remove() returns. A cancel_work_sync() in remove() can then race a notifier reschedule. devm_work_autocancel() and devm_delayed_work_autocancel() avoid that. They cancel the workers during devm release, before bci is freed. The current_worker is registered first, since devm will cancel in reverse order and bci->work can reschedule current_worker. [Move comment about order into the commit message]
Quoted source text, attributed separately from HOL analysis.