Description
In the Linux kernel, the following vulnerability has been resolved:

power: supply: cros_usbpd-charger: bound the EC-reported port count

cros_usbpd_charger_probe() reads two port counts from the EC and uses
one of them, num_charger_ports, as the loop bound when populating a
fixed-size array:

struct port_data *ports[EC_USB_PD_MAX_PORTS]; /* 8 entries */
...
for (i = 0; i < charger->num_charger_ports; i++)
charger->ports[charger->num_registered_psy++] = port;

Both num_usbpd_ports (from EC_CMD_USB_PD_PORTS) and num_charger_ports
(from EC_CMD_CHARGE_PORT_COUNT) are u8 values reported by the EC. The
only validation is a sanity check that compares the two EC-reported
values against each other:

if (num_charger_ports < num_usbpd_ports ||
num_charger_ports > num_usbpd_ports + 1)
return -EPROTO;

It never checks either count against EC_USB_PD_MAX_PORTS, the size of
the ports[] array. A malfunctioning, malicious or compromised EC that
reports num_usbpd_ports == num_charger_ports == N for any N > 8 (for
example both 255) passes this check, and the loop then writes N pointers
into the 8-entry ports[] array embedded in the devm_kzalloc()'d
charger_data, overflowing it by up to 255 - 8 = 247 entries (~1976
bytes): a slab out-of-bounds write.

Reject a port count larger than the ports[] array can hold.
Published: 2026-09-11
Score: 8.4 High
EPSS: < 1% Very Low
KEV: No
Impact: Out-of-bounds write in the Linux kernel's USB-C charger driver
Action: Immediate Patch
AI Analysis

Impact

In the Chrome OS USB Power Delivery charger driver, a flaw allows the embedded controller to report an inflated number of charger ports. The driver trusts this high count as a loop bound for an 8-slot array and writes past the array’s limits, corrupting kernel memory. This out-of-bounds write can lead to memory corruption, potential privilege escalation, or system instability.

Affected Systems

Linux kernel builds that include the cros_usbpd-charger driver, notably Chrome report charger port counts. The vulnerability applies to any kernel version that has not yet applied the fix referenced in the commit logs, as specific version ranges are not listed in the advisory.

Risk and Exploitability

The flaw does not provide a remote attack vector; an adversary would need access to the device’s EC or the ability to influence the EC’s reported values, typically requiring physical or firmware compromise. No public exploit has been 0.00168 indicates a very low exploitation probability, and the issue is not listed in the KEV catalog. The severity depends on the kernel’s privilege level, but kernel memory corruption poses a high impact if successfully exploited. Until a patch is applied, the risk could be considered moderate with potential for serious compromise if the EC can be manipulated.

Generated by OpenCVE AI on September 13, 2026 at 03:35 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Apply the kernel patch that adds a check against EC_USB_PD_MAX_PORTS before using num_charger_ports as a loop bound
  • Update the system to the latest kernel version that incorporates the fix
  • If a rapid update is unavailable, consider disabling the cros_usbpd-charger driver or restricting EC access to prevent malicious port count reports

Generated by OpenCVE AI on September 13, 2026 at 03:35 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Sun, 13 Sep 2026 06:45:00 +0000

Type Values Removed Values Added
Metrics cvssV3_1

{'score': 6.4, 'vector': 'CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H'}

cvssV3_1

{'score': 8.4, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H'}


Sat, 12 Sep 2026 12:15:00 +0000

Type Values Removed Values Added
Weaknesses CWE-787
References
Metrics threat_severity

None

cvssV3_1

{'score': 6.4, 'vector': 'CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H'}

threat_severity

Important


Fri, 11 Sep 2026 23:45:00 +0000

Type Values Removed Values Added
Description In the Linux kernel, the following vulnerability has been resolved: power: supply: cros_usbpd-charger: bound the EC-reported port count cros_usbpd_charger_probe() reads two port counts from the EC and uses one of them, num_charger_ports, as the loop bound when populating a fixed-size array: struct port_data *ports[EC_USB_PD_MAX_PORTS]; /* 8 entries */ ... for (i = 0; i < charger->num_charger_ports; i++) charger->ports[charger->num_registered_psy++] = port; Both num_usbpd_ports (from EC_CMD_USB_PD_PORTS) and num_charger_ports (from EC_CMD_CHARGE_PORT_COUNT) are u8 values reported by the EC. The only validation is a sanity check that compares the two EC-reported values against each other: if (num_charger_ports < num_usbpd_ports || num_charger_ports > num_usbpd_ports + 1) return -EPROTO; It never checks either count against EC_USB_PD_MAX_PORTS, the size of the ports[] array. A malfunctioning, malicious or compromised EC that reports num_usbpd_ports == num_charger_ports == N for any N > 8 (for example both 255) passes this check, and the loop then writes N pointers into the 8-entry ports[] array embedded in the devm_kzalloc()'d charger_data, overflowing it by up to 255 - 8 = 247 entries (~1976 bytes): a slab out-of-bounds write. Reject a port count larger than the ports[] array can hold.
Title power: supply: cros_usbpd-charger: bound the EC-reported port count
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References

Subscriptions

Linux Linux Kernel
cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published:

Updated: 2026-09-13T06:29:41.626Z

Reserved: 2026-09-11T19:38:34.710Z

Link: CVE-2026-89471

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-09-11T20:19:28.263

Modified: 2026-09-13T07:17:10.390

Link: CVE-2026-89471

cve-icon Redhat

Severity : Important

Publid Date: 2026-09-11T19:43:29Z

Links: CVE-2026-89471 - Bugzilla

cve-icon OpenCVE Enrichment

Updated: 2026-09-13T03:45:18Z

Weaknesses