# CVE-2026-89467: power: supply: qcom_battmgr: fix use-after-free

> A use-after-free in the Qualcomm battery manager driver allows local attackers to execute code or escalate privileges 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:** 21 Oct 2026
- **Also known as:** AZL-100112, BELL-CVE-2026-89467, DEBIAN-CVE-2026-89467, GHSA-6hqf-cg9r-x89w, UBUNTU-CVE-2026-89467

## What is CVE-2026-89467?

CVE-2026-89467 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: qcom_battmgr: fix use-after-free

qcom_battmgr_pdr_notify() queues enable_work when the PMIC GLINK service
comes up, and the worker recovers battmgr through container_of() to issue
firmware requests. The PMIC GLINK client stays on the client list until
its devres release action runs, so a PDR notification can keep queueing
the work, and a pending or running worker can access battmgr after devres
frees it.

Make enable_work device-managed with devm_work_autocancel(), registered
before the PMIC GLINK client is allocated. The devres cleanup then
releases the client first, so no further notification can queue the work,
and cancels the work before battmgr is freed.

This issue was found by an in-house static analysis tool.

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


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

Apply the vendor's patch.

## Is CVE-2026-89467 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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