CVE-2026-99581: platform/chrome: cros_usbpd_notify: Only use drvdata when parent is GOOG0004
In the Linux kernel, the following vulnerability has been resolved:
platform/chrome: crosusbpdnotify: Only use drvdata when parent is GOOG0004
crosusbpdnotifyprobeacpi() takes the EC device pointer from devgetdrvdata(dev->parent) and assumes it is a struct crosecdevice. That only holds when GOOG0003 is a child of GOOG0004. On older devices without that hierarchy, such as Google Nami, GOOG0003 and GOOG0004 are siblings under the ACPI EC (PNP0C09):
PNP0C09:00 (acpi-ec) |-- GOOG0003:00 (cros-usbpd-notify-acpi) -- GOOG0004:00 (croseclpcs)
Before commit db65a06d10b3 ("ACPI: EC: Convert the driver to a platform one") the parent platform device had no driver data, so the driver warned and continued without an EC pointer, as intended for these devices. Since that commit the ACPI EC driver stores its struct acpiec there, so the driver treats a struct acpiec as a struct crosecdevice and calls croseccmd() on it for every USB-C PD host event. Plugging or unplugging a charger then intermittently oopses, followed by soft lockups and a hung system:
BUG: unable to handle page fault for address: ffffffff9cf03220 #PF: supervisor write access in kernel mode Hardware name: Google Nami/Nami, BIOS 09/19/2019 Workqueue: kacpinotify acpiosexecutedeferred RIP: 0010:nativequeuedspinlockslowpath+0x29d/0x330 Call Trace: rawspinlockirqsave+0x59/0x80 mutexlock.constprop.0+0x129/0x930 croseccmdxfer+0x2a/0xf0 [crosecproto] croseccmdxferstatus+0x1a/0x90 [crosecproto] croseccmd+0xb7/0x140 [crosecproto] crosusbpdgeteventandnotify+0x42/0xc0 [crosusbpdnotify] acpievnotifydispatch+0x4e/0x70 acpiosexecutedeferred+0x1a/0x30
Only read the parent's driver data when the parent's ACPI node is GOOG0004, and otherwise continue without an EC pointer. While at it, drop the reference taken by fwnodegetparent().
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 7.3.5
Frequently Asked Questions
Which systems are affected by this issue?
Affected systems include older Chrome devices where the GOOG0003 USB-C PD notification device and GOOG0004 Chrome EC device are siblings beneath the ACPI EC device rather than having GOOG0003 as a child of GOOG0004. Google Nami is identified as an example of this layout.
What triggers the failure?
The failure is triggered when a USB-C PD host event causes the driver to issue a Chrome EC command using incorrectly interpreted parent driver data. Plugging in or unplugging a charger is specifically reported to intermittently cause an oops, soft lockups, and a hung system.
How can I determine whether a device has the vulnerable ACPI hierarchy?
Inspect the ACPI device tree. A vulnerable layout has GOOG0003 and GOOG0004 as siblings under PNP0C09 (acpi-ec), rather than GOOG0003 being a child of GOOG0004.
What can be done before a fix is applied?
Avoid triggering USB-C PD host events where possible, including charger plug and unplug operations, because these events can invoke the faulty path and hang the system.