# CVE-2026-89473: power: supply: bq25890: Fix power_supply reference leak

> A reference leak in the bq25890 power supply driver can lead to resource exhaustion and denial of service.

- **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-100322, BELL-CVE-2026-89473, DEBIAN-CVE-2026-89473, GHSA-82m6-wph9-4cgw, UBUNTU-CVE-2026-89473

## What is CVE-2026-89473?

CVE-2026-89473 is a denial of service 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: bq25890: Fix power_supply reference leak

bq25890_fw_probe() acquires a reference to a secondary charger using
power_supply_get_by_name(), but the reference is not released on later
probe failures or on driver detach.

In particular, failures after bq25890_fw_probe() returns successfully,
such as a failure in bq25890_hw_init(), also leak the reference.

Register a device-managed cleanup action immediately after acquiring
the secondary charger. This releases the reference on all subsequent
probe failures and on driver detach.

Found by code review.

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


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

Apply the vendor's patch.

## Is CVE-2026-89473 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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