# CVE-2026-89466: power: supply: qcom_battmgr: terminate the strings from firmware

> A missing null terminator in the Qualcomm battery manager driver allows reading adjacent kernel memory when firmware sends full-length strings.

- **Severity:** High 7.7 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H`)
- **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-100782, BELL-CVE-2026-89466, DEBIAN-CVE-2026-89466, GHSA-g9cw-qg44-9g2q, UBUNTU-CVE-2026-89466

## What is CVE-2026-89466?

CVE-2026-89466 is a high-severity 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: terminate the strings from firmware

The qcom_battmgr_sc8280xp_strcpy() takes a Pascal-style string when the
firmware sends one. Otherwise it copies all BATTMGR_STRING_LEN bytes and
leaves the destination without a terminator.

Those destinations are model_number, serial_number and oem_info, each
BATTMGR_STRING_LEN and declared next to each other. They go out to user
space as val->strval, which power_supply_format_property() prints with
"%s", so a firmware string that fills the whole field makes that read run
into the following members.

Use strscpy() so the copy always terminates, the way the SM8350 path
already does for the same field.

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


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

Apply the vendor's patch.

## Is CVE-2026-89466 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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