# CVE-2026-89474: power: supply: bq256xx: drain usb_work before freeing the charger

> A use-after-free in the bq256xx charger driver allows local attackers to cause a system crash or potentially execute code via race conditions.

- **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-100706, BELL-CVE-2026-89474, DEBIAN-CVE-2026-89474, GHSA-542v-8xr4-x59m, UBUNTU-CVE-2026-89474

## What is CVE-2026-89474?

CVE-2026-89474 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: bq256xx: drain usb_work before freeing the charger

The USB-PHY notifier queues usb_work, whose handler calls
power_supply_changed(bq->charger). The reset devm action only unregisters
the notifier and was registered before the power supplies, so devm frees
bq->charger on unwind before the action runs; a usb_work still queued can
then dereference it.

Register the reset action after the power supplies, so it unregisters
the notifiers and drains usb_work before the supplies are released.
Initialize usb_work and obtain the PHY references before registering
the notifiers, so the worker cannot run before the supplies exist.

Found by static analysis.

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


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

Apply the vendor's patch.

## Is CVE-2026-89474 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-89474 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-89474 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-89474/ (Markdown: https://insights.sbomify.com/CVE-2026-89474/index.md)
```

## Sources

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

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