CVE-2026-89470: power: supply: cros_usbpd: Limit port counts to EC_USB_PD_MAX_PORTS
Noroxi assessment
Priority: Monitor (action score 33/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.14% (FIRST EPSS).
- Someone with local access to the system can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 304a29ac55ba3ee6eceaf7d83d09cd9709f3bf60, 3262977a05b23d1be9fc86727a2b490ec997543e, 3ce9218639ff62d011eb8aca0943aa670a654c7b.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 304a29ac55ba3ee6eceaf7d83d09cd9709f3bf60, 3262977a05b23d1be9fc86727a2b490ec997543e, 3ce9218639ff62d011eb8aca0943aa670a654c7b or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Sep 11, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.1% · 3th percentile
- CWE
- —
Report tools
Action score
33
Monitor
Low priority for now.
- CVSS
- 33 / 40 · 8.4 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 8.4
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 4.20affected
- 3af15cfacd1eef7f223802d49a88cae23c509183 and later · before e951b65ef1699439079b723ca5c72cbe44771647affected · git
- 3af15cfacd1eef7f223802d49a88cae23c509183 and later · before 3ce9218639ff62d011eb8aca0943aa670a654c7baffected · git
- 3af15cfacd1eef7f223802d49a88cae23c509183 and later · before dce1750ddbd3380b1f6090dda2b07d2ebea2261daffected · git
- 3af15cfacd1eef7f223802d49a88cae23c509183 and later · before 3262977a05b23d1be9fc86727a2b490ec997543eaffected · git
- 3af15cfacd1eef7f223802d49a88cae23c509183 and later · before fd5f289cca04ad869b34fc9ccb647670bfdb60acaffected · git
- 3af15cfacd1eef7f223802d49a88cae23c509183 and later · before 4b1f2be1e1b74a50386ba718de3d62bfcf5ee701affected · git
- 3af15cfacd1eef7f223802d49a88cae23c509183 and later · before 304a29ac55ba3ee6eceaf7d83d09cd9709f3bf60affected · git
- 3af15cfacd1eef7f223802d49a88cae23c509183 and later · before 657cd3a42e937276262c0a8ae6b01a87004309deaffected · git
- before 4.20not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.190-1 | 6.1.190-1 |
| Debian:12 | linux-6.12 | before 6.12.111-1~deb12u1 | 6.12.111-1~deb12u1 |
| Debian:13 | linux | before 6.12.111-1 | 6.12.111-1 |
| Debian:14 | linux | before 7.2.6-1 | 7.2.6-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-89468Sep 11, 2026 · power: supply: lp8788-charger: fix use-after-free on remove0Monitor
- ← EarlierCVE-2026-89469Sep 11, 2026 · power: supply: lp8727: fix use-after-free in lp8727_release_irq()33Monitor
- Later →CVE-2026-89471Sep 11, 2026 · power: supply: cros_usbpd-charger: bound the EC-reported port count33Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 304a29ac55ba3ee6eceaf7d83d09cd9709f3bf60 | Vendor (CNA) |
| Linux Linux | 3262977a05b23d1be9fc86727a2b490ec997543e | Vendor (CNA) |
| Linux Linux | 3ce9218639ff62d011eb8aca0943aa670a654c7b | Vendor (CNA) |
| Linux Linux | 4b1f2be1e1b74a50386ba718de3d62bfcf5ee701 | Vendor (CNA) |
| Linux Linux | 657cd3a42e937276262c0a8ae6b01a87004309de | Vendor (CNA) |
| Linux Linux | dce1750ddbd3380b1f6090dda2b07d2ebea2261d | Vendor (CNA) |
| Linux Linux | e951b65ef1699439079b723ca5c72cbe44771647 | Vendor (CNA) |
| Linux Linux | fd5f289cca04ad869b34fc9ccb647670bfdb60ac | Vendor (CNA) |
| debian:linux | 6.1.190-1 · Debian:12 | Package registry (OSV) |
| debian:linux | 6.12.111-1 · Debian:13 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.111-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-1085 · Sep 14, 2026(Linux Kernel Güvenlik Bildirimi)
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/3262977a05b23d1be9fc86727a2b490ec997543e
- git.kernel.org/stable/c/3ce9218639ff62d011eb8aca0943aa670a654c7b
- git.kernel.org/stable/c/4b1f2be1e1b74a50386ba718de3d62bfcf5ee701
- git.kernel.org/stable/c/657cd3a42e937276262c0a8ae6b01a87004309de
- git.kernel.org/stable/c/dce1750ddbd3380b1f6090dda2b07d2ebea2261d
- git.kernel.org/stable/c/e951b65ef1699439079b723ca5c72cbe44771647
- git.kernel.org/stable/c/fd5f289cca04ad869b34fc9ccb647670bfdb60ac
Vendor advisories and official records. Exploit/PoC links are deliberately left out.