CVE-2026-89464 — power: supply: twl4030_charger: cancel workers via devm
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]
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.2% (30-day exploitation probability)+1
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux | ≥ d6ccc442b12102414c1343f0adacaa8a1aaa516c and < 9644c96ef8646c65d46caa5139a6631e29b79d6c≥ d6ccc442b12102414c1343f0adacaa8a1aaa516c and < e9fffe10bd791082263c1678f2f6cdd6d7b487e0≥ d6ccc442b12102414c1343f0adacaa8a1aaa516c and < c46c205bab0dfce4dd54aeb49da3f183e1fdfc63≥ d6ccc442b12102414c1343f0adacaa8a1aaa516c and < 72a2d6cd049f892853e4e2d8d8fc5e7d0244a458≥ d6ccc442b12102414c1343f0adacaa8a1aaa516c and < a4460e89d4088cfec2da5be33e265ef1a8e780e9≥ d6ccc442b12102414c1343f0adacaa8a1aaa516c and < b955da82db4170bdf1c784dc457287aa0c977378≥ d6ccc442b12102414c1343f0adacaa8a1aaa516c and < 6eba34732524067da2aad5ddfdfbc641ded10e9eversion 2.6.39 | Vulnerable | CVE Program (cve.org) e CISA ADP |
EPSS over time FIRST
Oct 15, 2026 → Oct 24, 2026 · 9 reading(s) · max 0.17%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Not enough vector or weakness data: use the affected application’s logs as a starting point.
Timeline
What happened to this CVE, newest first.
- 2026
- Record published
- Affected products added · linux/linux
- Source status changed · → Received
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× References added · Oct 19, 2026 – Oct 19, 2026
- 1× Official description updated · Oct 15, 2026 – Oct 15, 2026
References
9 on the record
- git.kernel.org/stable/c/c46c205bab0dfce4dd54aeb49da3f183e1fdfc63
- nvd.nist.gov/vuln/detail/CVE-2026-89464
- git.kernel.org/stable/c/e9fffe10bd791082263c1678f2f6cdd6d7b487e0
- github.com/advisories/GHSA-pf33-mh27-rp5j
- git.kernel.org/stable/c/9644c96ef8646c65d46caa5139a6631e29b79d6c
- git.kernel.org/stable/c/6eba34732524067da2aad5ddfdfbc641ded10e9e
- git.kernel.org/stable/c/a4460e89d4088cfec2da5be33e265ef1a8e780e9
- git.kernel.org/stable/c/b955da82db4170bdf1c784dc457287aa0c977378
- git.kernel.org/stable/c/72a2d6cd049f892853e4e2d8d8fc5e7d0244a458
Elsewhere on this site
Related CVEs (same products)
- Unknown CVE-2026-99086 dm-integrity: validate the superblock on resume 1d
- Unknown CVE-2026-99087 dm-integrity: fix NULL pointer dereference when the 'R' flag is used 1d
- Unknown CVE-2026-99080 fs: Free any excess xarray nodes in clear_inode() 1d
- Unknown CVE-2026-99084 readdir: take no inode lock on an immutable directory 1d
- Unknown CVE-2026-99085 sched_ext: Fix CPU hotplug hang when a dying CPU's tasks sit in the BPF scheduler 1d
- Critical CVE-2026-99079 net/mlx5e: Prevent stale XSK buffer release on refill retry 1d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CVSS score published by NVD, the CNA, CISA or GitHub so far.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-89464 is "power: supply: twl4030_charger: cancel workers via devm", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. EPSS 0.17% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.