From mboxrd@z Thu Jan 1 00:00:00 1970 Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.remote-ip=100.103.45.18 ARC-Seal: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; cv=none; t=1795153970; b=HI3nYukhZ+x61s8SPiK0Qb1rqS/L92uZbauRg0645MdchzcvE/7A4/Y64qBp7dk7YvIG PRrrvPW8YZkDptL5aeIPF22l7I1hwqlvA0W/Ak3t1O3Q0Hdnep3zgpRwxknePXQ/plKK+ M7+yWkNNze7OG2Hi/Vvx91c4MavswfLY9N6mpsXwJLoo9MaGf6izcDeZu68mvpx14nA1z gabZ+jWvJJiLaWbYrpjx1j4Iu3nFdIxnTqD/ohJJlGF++cE1QS/PbYRjcmSBSwRzwWpe6 9ESP10KU48AzPMEXxrbcp2gAyzruIxv3QWP1j05pF6d3bc2WYqVr16Kc9PWtQstEj5A== ARC-Message-Signature: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; c=relaxed/relaxed; t=1795153970; h=Received:DKIM-Signature:From:To:Cc:Subject:Date:Message-ID:X-Mailer: Reply-To:MIME-Version:Lines:X-Developer-Signature:X-Developer-Key: Content-Transfer-Encoding; bh=cl/atvXBpqExP/ZRS803nu+hk1fw5c1DPXs+qRXx8Sg=; b=AYTMDCihzzMqbwrHMNM+gKAei8jhCJv2pQpWaB6VSsGE04N3hxpUHN6w8nz0F3JSTV3Q I4yUhyeRPqcDMSVZyNfoNH5tgglz9j7TMEbOgwzEmhSo/7sNbg1NctFQ2BHzKwnDD4NLd uMzb1Gx1OO6OhKkv0LRLPUW9OwY1Nv7s+c0GnBQ7UMAnNoCiIyWbUXNlU6atqOpquX3ED C3o6IYqUUORY7aNng/+LJlb0DFC53zxSsPRinUfsGUCrNiJsmgwFRsOWHIlWKm9zMycG+ qmLlcY2OVKj8YSfKZ16VmIm3S769RIaw9LtWa5XFzgsxYKnt3LbxztC8WUjutB8JKdA== ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dkim=pass header.d=linuxfoundation.org header.i=@linuxfoundation.org header.a=rsa-sha256 header.s=korg header.b=bcTehbOi; arc=none smtp.remote-ip=100.103.45.18 Received: from smtp.kernel.org (quasi.space.kernel.org [100.103.45.18]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (prime256v1)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 40A15606A320 for ; Fri, 20 Nov 2026 05:52:50 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.a=rsa-sha256 header.s=korg header.b=bcTehbOi Received: by smtp.kernel.org (Postfix) with ESMTPSA id 654B71F000CF; Fri, 20 Nov 2026 05:52:49 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1795153970; bh=cl/atvXBpqExP/ZRS803nu+hk1fw5c1DPXs+qRXx8Sg=; h=From:To:Cc:Subject:Date:Reply-To; b=bcTehbOiLo/B/ab0iZ/3PUEFD5Vs+M+Aw6ZHllTAvCrLY7DCi9TlMHv38FrBNm5TD /im7B9A2wosxRyCsCJJqcXOgBqeXYKCdqvgFNzIWwed18SEkYI4ZDtHEcu37fQ0afp j5kJeYDsUfmuHsDAXTFzPnXYVMIc9XbEdOym+Sws= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-99581: platform/chrome: cros_usbpd_notify: Only use drvdata when parent is GOOG0004 Date: Fri, 20 Nov 2026 06:49:27 +0100 Message-ID: <2026112019-CVE-2026-99581-ddab@gregkh> X-Mailer: git-send-email 2.56.1 Reply-To: , X-Mailing-List: linux-cve-announce@vger.kernel.org List-Id: List-Post: List-Help: List-Subscribe: List-Unsubscribe: List-Owner: Precedence: list MIME-Version: 1.0 X-Developer-Signature: v=1; a=openpgp-sha256; l=3600; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=WPwKh0VDo8Vd6x1koT+aixkCMhS2hglUiQh0aU4QA/8=; b=owGbwMvMwCRo6H6F97bub03G02pJDFn/78cfNxLdWvd4tc6GL+7BLH/5DjCWLuiPfeCS9Y/3a kBWsuOHjlgWBkEmBlkxRZYv23iO7q84pOhlaHsaZg4rE8gQBi5OAZjInbkMCw5bzMp6l5LPJrb6 0N2X827pPVutnsgwz75waozp5VMPTC+dO3M89dcG3Z4aaQA= X-Developer-Key: i=gregkh@linuxfoundation.org; a=openpgp; fpr=F4B60CC5BF78C2214A313DCB3147D40DDB2DFB29 Content-Transfer-Encoding: 8bit From: Greg Kroah-Hartman Description =========== 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(). The Linux kernel CVE team has assigned CVE-2026-99581 to this issue. Affected and fixed versions =========================== Issue introduced in 6.19 with commit e4ee0bb077cd7d70207647a0106f6ea6a74c2636 and fixed in 7.3.5 with commit 4de4a28e514ea2cf9a91d198b66cda7f02ad5edb Issue introduced in 6.19 with commit e4ee0bb077cd7d70207647a0106f6ea6a74c2636 and fixed in 7.4-rc1 with commit ca75b38b1a3c2eabe81d231dae4ea180cf6287cd Please see https://www.kernel.org for a full list of currently supported kernel versions by the kernel community. Unaffected versions might change over time as fixes are backported to older supported kernel versions. The official CVE entry at https://cve.org/CVERecord/?id=CVE-2026-99581 will be updated if fixes are backported, please check that for the most up to date information about this issue. Affected files ============== The file(s) affected by this issue are: drivers/platform/chrome/cros_usbpd_notify.c Mitigation ========== The Linux kernel CVE team recommends that you update to the latest stable kernel version for this, and many other bugfixes. Individual changes are never tested alone, but rather are part of a larger kernel release. Cherry-picking individual commits is not recommended or supported by the Linux kernel community at all. If however, updating to the latest release is impossible, the individual changes to resolve this issue can be found at these commits: https://git.kernel.org/stable/c/4de4a28e514ea2cf9a91d198b66cda7f02ad5edb https://git.kernel.org/stable/c/ca75b38b1a3c2eabe81d231dae4ea180cf6287cd