# CVE-2026-89475: power: supply: bq24257: fix use-after-free on remove

> A use-after-free in the bq24257 power supply driver allows local attackers to execute arbitrary code or escalate privileges via race conditions during device removal.

- **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-100208, BELL-CVE-2026-89475, DEBIAN-CVE-2026-89475, GHSA-pg63-6v2p-p54j, UBUNTU-CVE-2026-89475

## What is CVE-2026-89475?

CVE-2026-89475 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: bq24257: fix use-after-free on remove

The STAT-pin interrupt is devm-managed, so it stays armed until the devm
cleanup that runs after remove() returns. remove() cancels
bq->iilimit_setup_work while the threaded handler can still fire; that
handler reschedules the work and dereferences bq, so the work runs
against freed memory once devm frees bq.

Make the delayed work device-managed with devm_delayed_work_autocancel(),
registered before the interrupt request. The devm cleanup then releases
the interrupt first, so the handler can no longer reschedule the work,
and cancels the work before bq is freed. The explicit
cancel_delayed_work_sync() in remove() is no longer needed and is dropped.

Found by static analysis.

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


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

Apply the vendor's patch.

## Is CVE-2026-89475 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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