CVE-2026-89471
CVE CVE-2026-89471EUVD EUVD-2026-76377Published 2026-09-11T19:43:29.000ZLast changed 2026-09-14T12:00:08.000ZCVSS 8.4
What the advisory describes
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.
Source: EUVD (ENISA), in the words of the advisory.
Products the advisory names
These come from the advisory itself, not from any check we performed.
- Linux — Linux f68b883e8fad23ed0ac4756d91594809d78678ed <48355ce49359740f52e94d3623f6fc557ce341f0; patch: 0; patch: 6.12.109; f68b883e8fad23ed0ac4756d91594809d78678ed <c46c9f447415ca802afab51dea1eafc08ddff1c6; patch: 6.1.188; 4.19; patch: 6.6.157; patch: 7.3-rc1; f68b883e8fad23ed0ac4756d91594809d78678ed <78be8b7403ff7638162438b664a07d19da76059e; patch: 7.2.4; f68b883e8fad23ed0ac4756d91594809d78678ed <fd29d08ee487f3bf50f2575aaa74f78a74b09b21; f68b883e8fad23ed0ac4756d91594809d78678ed <2746d502b12b343384fb747bdef9cbcfbd7444a2; f68b883e8fad23ed0ac4756d91594809d78678ed <0b5096f6804161b61451b1cec0e38678630be849; patch: 5.10.270; patch: 5.15.221; f68b883e8fad23ed0ac4756d91594809d78678ed <3d1e01443b221081258ff34ea0cdd0431e4ff62e; f68b883e8fad23ed0ac4756d91594809d78678ed <a1905375dfc0b9612bbee52fc066e3a70c0d671d; patch: 6.18.50
The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.
Carried in the product catalogue
An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.
- Linux — Linux
Does this concern one of your customers?
This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.
Try it for 28 daysPatchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.