CVE-2026-99581 in Linuxinfo

Summary

by MITRE • 11/20/2026

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

platform/chrome: cros_usbpd_notify: Only use drvdata when parent is GOOG0004

cros_usbpd_notify_probe_acpi() takes the EC device pointer from dev_get_drvdata(dev->parent) and assumes it is a struct cros_ec_device. 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 (cros_ec_lpcs)

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 acpi_ec there, so the driver treats a struct acpi_ec as a struct cros_ec_device and calls cros_ec_cmd() 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: kacpi_notify acpi_os_execute_deferred RIP: 0010:native_queued_spin_lock_slowpath+0x29d/0x330 Call Trace: _raw_spin_lock_irqsave+0x59/0x80 __mutex_lock.constprop.0+0x129/0x930 cros_ec_cmd_xfer+0x2a/0xf0 [cros_ec_proto]
cros_ec_cmd_xfer_status+0x1a/0x90 [cros_ec_proto]
cros_ec_cmd+0xb7/0x140 [cros_ec_proto]
cros_usbpd_get_event_and_notify+0x42/0xc0 [cros_usbpd_notify]
acpi_ev_notify_dispatch+0x4e/0x70 acpi_os_execute_deferred+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 fwnode_get_parent().

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Analysis

by VulDB Data Team • 11/21/2026

The vulnerability identified in the Linux kernel involves a critical type confusion error within the cros_usbpd_notify driver, specifically affecting systems where Google Chrome OS USB Power Delivery notifications are managed through ACPI interfaces. This flaw arises from an incorrect assumption regarding the device hierarchy and the structure of data stored in parent devices. The function cros_usbpd_notify_probe_acpi retrieves a pointer to the Embedded Controller (EC) device by calling dev_get_drvdata on the parent device, expecting this pointer to reference a struct cros_ec_device. However, this expectation is only valid when the ACPI node GOOG0003 is strictly a child of GOOG0004. On older hardware architectures, such as Google Nami devices, these nodes are siblings under the generic ACPI EC driver identified by PNP0C09 rather than being in a parent-child relationship involving the specific Chrome OS EC drivers.

Prior to commit db65a06d10b3, which converted the ACPI EC driver into a platform driver, the parent platform device did not store any meaningful driver data at that location. Consequently, the cros_usbpd_notify driver would receive a null or invalid pointer and correctly warn about the missing EC pointer while continuing operation without it. This behavior was functionally correct for devices lacking the specific GOOG0004 hierarchy because they do not require interaction with the Chrome OS EC via this notification path. The introduction of the platform conversion changed the internal state management of the ACPI EC driver, causing it to store a struct acpi_ec pointer in the same location previously occupied by nothing or null data. This change inadvertently created a scenario where the cros_usbpd_notify driver interprets an acpi_ec structure as if it were a cros_ec_device structure.

The operational impact of this type confusion is severe and leads to system instability. When a USB-C power delivery event occurs, such as plugging or unplugging a charger, the kernel attempts to process the notification by calling cros_ec_cmd on what it believes is an EC device but is actually an ACPI EC handle. This mismatch results in invalid memory access patterns because the two structures have different layouts and expected behaviors. The system experiences page faults due to supervisor write access violations in kernel mode, leading to soft lockups and hung systems. The call trace indicates that the crash occurs during a spin lock operation within cros_ec_cmd_xfer, triggered by acpi_os_execute_deferred handling ACPI notify events. This represents a denial of service condition where normal hardware interactions cause complete system freezes requiring hard resets.

From a vulnerability classification perspective, this issue aligns with CWE-823, Use of Out-of-range Pointer Offset, and more broadly CWE-94, Improper Control of Generation of Code (Code Injection), as the kernel executes code based on misinterpreted data structures leading to unauthorized memory operations. In terms of MITRE ATT&CK mapping, this vulnerability facilitates local privilege escalation or denial of service through improper input validation and type confusion within the operating system core components. The root cause is a lack of strict device tree hierarchy verification before dereferencing pointers derived from driver-specific data slots that may be repurposed by other drivers in different hardware configurations.

To mitigate this vulnerability, developers must ensure that the cros_usbpd_notify driver only accesses parent driver data when it can definitively confirm that the parent ACPI node corresponds to GOOG0004. If the parent is not GOOG0004, the driver should continue operation without attempting to use an EC pointer, effectively ignoring USB-PD notifications for devices where this mechanism is unsupported or incorrectly configured in the firmware. Additionally, any references obtained via fwnode_get_parent that are no longer needed after determining the correct device hierarchy should be explicitly dropped to prevent reference count leaks and potential memory management issues. This fix restores compatibility with older hardware designs while maintaining security integrity by preventing invalid kernel pointer dereferences.

Responsible

Linux

Reservation

09/25/2026

Disclosure

11/20/2026

Moderation

accepted

CPE

ready

EPSS

0.00198

KEV

no

Activities

very low

Sources

Do you know our Splunk app?

Download it now for free!