# CVE-2026-89464: power: supply: twl4030_charger: cancel workers via devm

> A use-after-free vulnerability in the Linux kernel twl4030 charger driver allows local attackers to cause a denial of service or potentially execute code.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 11 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-100617, BELL-CVE-2026-89464, DEBIAN-CVE-2026-89464, GHSA-pf33-mh27-rp5j, UBUNTU-CVE-2026-89464

## What is CVE-2026-89464?

CVE-2026-89464 is an use after free vulnerability in Linux, published on 11 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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]

## Which versions are affected by CVE-2026-89464?


## How do I fix CVE-2026-89464?

Apply the vendor's patch.

## Is CVE-2026-89464 being exploited?

There is no known exploitation of CVE-2026-89464 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-89464 and fix it if it is affected.

What it is: CVE-2026-89464 is an use after free vulnerability in Linux, published on 11 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-89464 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-89464/ (Markdown: https://insights.sbomify.com/CVE-2026-89464/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-89464
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-89464
- OSV: https://osv.dev/vulnerability/CVE-2026-89464

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-89464/
Summaries are generated and may contain mistakes; the official description above is the record.