power: supply: cros_usbpd-charger: bound the EC-reported port count
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.10.270, 5.15.221, 6.1.188, 6.6.157, 6.12.109, and 2 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From f68b883e8fad23ed0ac4756d91594809d78678ed · fixed in 0b5096f6804161b61451b1cec0e38678630be849; From f68b883e8fad23ed0ac4756d91594809d78678ed · fixed in c46c9f447415ca802afab51dea1eafc08ddff1c6; From f68b883e8fad23ed0ac4756d91594809d78678ed · fixed in a1905375dfc0b9612bbee52fc066e3a70c0d671d; From f68b883e8fad23ed0ac4756d91594809d78678ed · fixed in 2746d502b12b343384fb747bdef9cbcfbd7444a2; From f68b883e8fad23ed0ac4756d91594809d78678ed · fixed in fd29d08ee487f3bf50f2575aaa74f78a74b09b21; From f68b883e8fad23ed0ac4756d91594809d78678ed · fixed in 78be8b7403ff7638162438b664a07d19da76059e; From f68b883e8fad23ed0ac4756d91594809d78678ed · fixed in 3d1e01443b221081258ff34ea0cdd0431e4ff62e; From f68b883e8fad23ed0ac4756d91594809d78678ed · fixed in 48355ce49359740f52e94d3623f6fc557ce341f0
- Linux Linux
4.19
- KernelLinux
From 4.19.0 · fixed in 5.10.270; From 5.11.0 · fixed in 5.15.221; From 5.16.0 · fixed in 6.1.188; From 6.2.0 · fixed in 6.6.157; From 6.7.0 · fixed in 6.12.109; From 6.13.0 · fixed in 6.18.50; From 6.19.0 · fixed in 7.2.4
References 8
git.kernel.org
- stable/c/0b5096f6804161b61451b1cec0e38678630be849
- stable/c/c46c9f447415ca802afab51dea1eafc08ddff1c6
- stable/c/a1905375dfc0b9612bbee52fc066e3a70c0d671d
- stable/c/2746d502b12b343384fb747bdef9cbcfbd7444a2
- stable/c/fd29d08ee487f3bf50f2575aaa74f78a74b09b21
- stable/c/78be8b7403ff7638162438b664a07d19da76059e
- stable/c/3d1e01443b221081258ff34ea0cdd0431e4ff62e
- stable/c/48355ce49359740f52e94d3623f6fc557ce341f0