CVE-2026-89464: power: supply: twl4030_charger: cancel workers via devm
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.17% (FIRST EPSS).
- Fixed version: Linux Linux 6eba34732524067da2aad5ddfdfbc641ded10e9e, 72a2d6cd049f892853e4e2d8d8fc5e7d0244a458, 9644c96ef8646c65d46caa5139a6631e29b79d6c.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 6eba34732524067da2aad5ddfdfbc641ded10e9e, 72a2d6cd049f892853e4e2d8d8fc5e7d0244a458, 9644c96ef8646c65d46caa5139a6631e29b79d6c or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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]
- Published
- Sep 11, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.1% · 6th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 2.6.39affected
- d6ccc442b12102414c1343f0adacaa8a1aaa516c and later · before 9644c96ef8646c65d46caa5139a6631e29b79d6caffected · git
- d6ccc442b12102414c1343f0adacaa8a1aaa516c and later · before e9fffe10bd791082263c1678f2f6cdd6d7b487e0affected · git
- d6ccc442b12102414c1343f0adacaa8a1aaa516c and later · before c46c205bab0dfce4dd54aeb49da3f183e1fdfc63affected · git
- d6ccc442b12102414c1343f0adacaa8a1aaa516c and later · before 72a2d6cd049f892853e4e2d8d8fc5e7d0244a458affected · git
- d6ccc442b12102414c1343f0adacaa8a1aaa516c and later · before a4460e89d4088cfec2da5be33e265ef1a8e780e9affected · git
- d6ccc442b12102414c1343f0adacaa8a1aaa516c and later · before b955da82db4170bdf1c784dc457287aa0c977378affected · git
- d6ccc442b12102414c1343f0adacaa8a1aaa516c and later · before 6eba34732524067da2aad5ddfdfbc641ded10e9eaffected · git
- before 2.6.39not affected · semver
- 5.15.221 and later · up to and including 5.15.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.190-1 | 6.1.190-1 |
| Debian:12 | linux-6.12 | before 6.12.111-1~deb12u1 | 6.12.111-1~deb12u1 |
| Debian:13 | linux | before 6.12.111-1 | 6.12.111-1 |
| Debian:14 | linux | before 7.2.6-1 | 7.2.6-1 |
| openSUSE:Tumbleweed | kernel-source | before 7.2.7-1.1 | 7.2.7-1.1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-89462Sep 11, 2026 · power: supply: max17040: propagate register read errors0Monitor
- ← EarlierCVE-2026-89463Sep 11, 2026 · power: supply: ucs1002: fix use-after-free on remove0Monitor
- Later →CVE-2026-89465Sep 11, 2026 · power: supply: rt9455: quiesce delayed work before teardown33Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 6eba34732524067da2aad5ddfdfbc641ded10e9e | Vendor (CNA) |
| Linux Linux | 72a2d6cd049f892853e4e2d8d8fc5e7d0244a458 | Vendor (CNA) |
| Linux Linux | 9644c96ef8646c65d46caa5139a6631e29b79d6c | Vendor (CNA) |
| Linux Linux | a4460e89d4088cfec2da5be33e265ef1a8e780e9 | Vendor (CNA) |
| Linux Linux | b955da82db4170bdf1c784dc457287aa0c977378 | Vendor (CNA) |
| Linux Linux | c46c205bab0dfce4dd54aeb49da3f183e1fdfc63 | Vendor (CNA) |
| Linux Linux | e9fffe10bd791082263c1678f2f6cdd6d7b487e0 | Vendor (CNA) |
| debian:linux | 6.1.190-1 · Debian:12 | Package registry (OSV) |
| debian:linux | 6.12.111-1 · Debian:13 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.111-1~deb12u1 · Debian:12 | Package registry (OSV) |
| opensuse:kernel-source | 7.2.7-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-1085 · Sep 14, 2026(Linux Kernel Güvenlik Bildirimi)
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (6 more)Show less
- git.kernel.org/stable/c/72a2d6cd049f892853e4e2d8d8fc5e7d0244a458
- git.kernel.org/stable/c/9644c96ef8646c65d46caa5139a6631e29b79d6c
- git.kernel.org/stable/c/a4460e89d4088cfec2da5be33e265ef1a8e780e9
- git.kernel.org/stable/c/b955da82db4170bdf1c784dc457287aa0c977378
- git.kernel.org/stable/c/c46c205bab0dfce4dd54aeb49da3f183e1fdfc63
- git.kernel.org/stable/c/e9fffe10bd791082263c1678f2f6cdd6d7b487e0
Vendor advisories and official records. Exploit/PoC links are deliberately left out.