# CVE-2026-89797: power: supply: ab8500_fg: fix use-after-free on remove

> A use-after-free in the ab8500 fuel gauge driver allows local attackers to cause a denial of service or potentially execute code 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:** 16 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-101252, BELL-CVE-2026-89797, DEBIAN-CVE-2026-89797, GHSA-vg3c-mvmw-87jj, UBUNTU-CVE-2026-89797

## What is CVE-2026-89797?

CVE-2026-89797 is an use after free vulnerability in Linux, published on 16 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: ab8500_fg: fix use-after-free on remove

ab8500_fg_remove() destroys the driver workqueue while the threaded
interrupt handlers are still armed; they are devm-managed and freed
only after ->remove() returns, so a handler that fires in that
window queues work on the freed workqueue.

Tear the workqueue down through devm instead, registering its cleanup
after the power supply and before the interrupt requests.  devm then
frees the interrupts first, so the handlers can no longer queue work,
before disabling the delayed and plain work items and destroying the
workqueue.  Disabling the items, rather than cancelling them, keeps
them disabled so no producer (including the power-supply
external_power_changed callback) can requeue them.

Found by an in-house static analysis tool.

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


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

Apply the vendor's patch.

## Is CVE-2026-89797 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-89797 is an use after free vulnerability in Linux, published on 16 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-89797 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-89797/ (Markdown: https://insights.sbomify.com/CVE-2026-89797/index.md)
```

## Sources

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

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