# CVE-2026-89470: power: supply: cros_usbpd: Limit port counts to EC_USB_PD_MAX_PORTS

> A malicious embedded controller can trigger an out-of-bounds write in the Linux kernel cros_usbpd-charger driver, leading to memory corruption and potential code execution.

- **Severity:** High 8.4 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/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-100842, BELL-CVE-2026-89470, DEBIAN-CVE-2026-89470, GHSA-xchr-hvc5-jhvq, UBUNTU-CVE-2026-89470

## What is CVE-2026-89470?

CVE-2026-89470 is a high-severity memory corruption 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: cros_usbpd: Limit port counts to EC_USB_PD_MAX_PORTS

Currently the cros_usbpd-charger driver probe iterates based on raw
charger port count returned by the embedded controller. The only check
is against the number of USB PD ports which the embedded controller
also defines. A malicious embedded controller could return an inaccurate
port count (up to 255) resulting in an out of bounds write and
subsequent memory corruption.

Update helper functions in cros_usbpd-charger to limit port counts to
EC_USB_PD_MAX_PORTS.

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


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

Apply the vendor's patch.

## Is CVE-2026-89470 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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