PatchSiren cyber security CVE debrief
CVE-2026-89470 Linux CVE debrief
A vulnerability in the Linux kernel's cros_usbpd-charger driver could allow a malicious embedded controller to return an inaccurate port count, potentially resulting in an out of bounds write and subsequent memory corruption. This issue arises from the driver's failure to properly validate port counts returned by the embedded controller, which could lead to memory corruption and potential denial of service. Linux kernel developers and maintainers should verify and limit port counts to EC_USB_PD_MAX_PORTS in cros_usbpd-charger.
- Vendor
- Linux
- Product
- Unknown
- CVSS
- HIGH 8.4
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-09-11
- Original CVE updated
- 2026-09-11
- Advisory published
- 2026-09-11
- Advisory updated
- 2026-09-11
Who should care
Linux kernel developers and maintainers, cros_usbpd-charger users and deployers, and security teams responsible for vulnerability management and patching should be aware of this vulnerability and take necessary actions to verify and limit port counts in cros_usbpd-charger. Additionally, operators and administrators of affected systems should review and update their deployments to prevent potential memory corruption and denial of service.
Why it matters
A vulnerability in the Linux kernel's cros_usbpd-charger driver could allow a malicious embedded controller to return an inaccurate port count, potentially resulting in an out of bounds write and subsequent memory corruption. Linux kernel developers and maintainers should verify and limit port counts to EC_USB_PD_MAX_PORTS in cros_usbpd-charger.
- Potential memory corruption due to out of bounds write
- Possible denial of service due to memory corruption
- Need for verification of port count validation in cros_usbpd-charger
Technical summary
The cros_usbpd-charger driver in the Linux kernel does not properly validate port counts returned by the embedded controller, potentially allowing an attacker to cause an out of bounds write and memory corruption. This vulnerability can be mitigated by limiting port counts to EC_USB_PD_MAX_PORTS in cros_usbpd-charger. Affected Linux kernel developers and maintainers should review and update the driver to ensure proper validation of port counts and prevent potential memory corruption. The vulnerability highlights the importance of robust validation and input sanitization in kernel drivers.
Defensive priority
Verify and limit port counts to EC_USB_PD_MAX_PORTS in cros_usbpd-charger
Recommended defensive actions
- Verify port counts are limited to EC_USB_PD_MAX_PORTS in cros_usbpd-charger
- Review embedded controller port count validation
- Update cros_usbpd-charger to the latest version
- Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
- Review compensating controls for exposed systems while remediation is scheduled and verified
- Check relevant monitoring, detection, and logs for exposed assets that need extra review
- whoShouldCare
Evidence notes
The CVE record and NVD entry provide limited information about the vulnerability. The Linux kernel patch notes indicate a fix for an out of bounds write issue in the cros_usbpd-charger driver. Further review of the driver code and patch notes reveals that the fix involves limiting port counts to EC_USB_PD_MAX_PORTS. However, the exact scope of affected systems and potential impact on various deployments remains unclear. Defenders should verify port count validation in cros_usbpd-charger and review embedded controller port count limits
Sources and references
Verified primary and authoritative sources
-
CVE-2026-89470 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-89470
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-89470 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-89470
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/304a29ac55ba3ee6eceaf7d83d09cd9709f3bf60
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/4b1f2be1e1b74a50386ba718de3d62bfcf5ee701
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/657cd3a42e937276262c0a8ae6b01a87004309de
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/fd5f289cca04ad869b34fc9ccb647670bfdb60ac
416baaa9-dc9f-4396-8d5f-8c081fb06d67
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.