From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-alma10-1.taild15c8.ts.net [100.103.45.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 1486E581232 for ; Fri, 11 Sep 2026 19:49:44 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=100.103.45.18 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1789156197; cv=none; b=Ocaioyd7aVjoOO9o0QPPsiJPbgIZr8uvm7A+eVJ0Tbvu8CaIgCU39oZpw0I/rDc89beHiyAHKXe5D+BSC65DlkvYAe4tenD9uS6v60wyEQC+FP9scAC7RJgbr0AhvtVmI394XWY3ohu68R8gnAQV0iTPXwxNlX5b2AlxRh8RftI= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1789156197; c=relaxed/simple; bh=LNAcwyGtsVLRFJlQysRKT2rKF0WC1CKWIR+tl2A/C30=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=IpnoCcna6GnI/8U2u0qi5JMCkO18bOERZiIRzqEZ10eAqZEmvQlFzoUT5KX9/R/bhLZ3iKOU/a2wMFk2qSAWQNdb0+VLjAzRPjlO3ir4n248IpN9AEYnhqIQ5rGuFTBvcc0SzZnbHSt189hWTvGr80Y8nv4FD97jtFw+8msId+s= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=JLek/dZg; arc=none smtp.client-ip=100.103.45.18 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b="JLek/dZg" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 6A7EC1F0089A; Fri, 11 Sep 2026 19:49:43 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1789156184; bh=UIkLpgWdg6ov9CMuSaDkb3Bsyg+IY/jcSRsAWJgE+FA=; h=From:To:Cc:Subject:Date:Reply-To; b=JLek/dZg6BaSpz5k4KJrLjSrBUCGEiRSB1Vyjjkum+I+bAzVr/Zq8OKubE5oxbEsg ZAJCXkaWmyY0DXYOu9EmNTNx/RjOQGpH52APy4brsL0AqJqO1Jdi6DoYzcJxxo+gvT Gu/o23ldWOxaPTwN8PLHsD5mcBJJzBSrq2e70q9Y= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-81015: platform/x86/amd/pmc: Fix LPS0 and debugfs leaks when STB init fails Date: Fri, 11 Sep 2026 21:42:01 +0200 Message-ID: <2026091154-CVE-2026-81015-3515@gregkh> X-Mailer: git-send-email 2.55.0 Reply-To: , Precedence: bulk X-Mailing-List: linux-cve-announce@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-Developer-Signature: v=1; a=openpgp-sha256; l=3325; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=XhVgO0zLtLBTCBX420GZndO0UlKgojBrxzVIW8inTXo=; b=owGbwMvMwCRo6H6F97bub03G02pJDFlLIt1MFrn07bqR9kf90650t8Py5eITLtlEqkUua5lxf /02Nr+XHbEsDIJMDLJiiixftvEc3V9xSNHL0PY0zBxWJpAhDFycAjARjt8MC27O6Pmg9+ft6m3z 3y+exfnSmot9czzDPO0yD1mpzCeX/j8SrDq+sHHF5HdpBwA= 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/x86/amd/pmc: Fix LPS0 and debugfs leaks when STB init fails amd_pmc_probe() registers the LPS0 s2idle handler with acpi_register_lps0_dev() and creates the driver's debugfs directory before calling amd_stb_s2d_init(), which is the last step in probe that can fail. When amd_stb_s2d_init() fails (for example the S2D telemetry region cannot be ioremapped on a long-running system, or the SMU rejects the S2D setup) the error path only calls pci_dev_put() and returns. This leaves amd_pmc_s2idle_dev_ops on the global lps0_s2idle_devops_head list and leaks the debugfs directory, while the devm-managed resources backing the handler are torn down. Reloading the module then walks the corrupted list in acpi_register_lps0_dev() and hits: list_add corruption. next->prev should be prev, but was NULL. kernel BUG at lib/list_debug.c:29! acpi_register_lps0_dev+0x44/0x80 amd_pmc_probe+0x224/0x380 [amd_pmc] platform_probe+0x67/0x90 Even without a reload, the stale registration means the next s2idle transition calls into torn-down driver state. Unwind the debugfs directory and the LPS0 registration on the amd_stb_s2d_init() error path. acpi_unregister_lps0_dev() is safe to call unconditionally here: it is guarded on the same conditions as acpi_register_lps0_dev(), which is exactly what amd_pmc_remove() already relies on. The Linux kernel CVE team has assigned CVE-2026-81015 to this issue. Affected and fixed versions =========================== Issue introduced in 6.14 with commit 83ad6974dd3bf34c080b3c08d36d02ebc3bd6da8 and fixed in 6.18.50 with commit bc9aa5fe21c3966c80647ed6574b94b863f23c62 Issue introduced in 6.14 with commit 83ad6974dd3bf34c080b3c08d36d02ebc3bd6da8 and fixed in 7.2.4 with commit 30e5f4d0cd0be655c800f10ae3e530391aa6c1b5 Issue introduced in 6.14 with commit 83ad6974dd3bf34c080b3c08d36d02ebc3bd6da8 and fixed in 7.3-rc1 with commit 76f650a76d6a36a4bee79d94db90a0e935a95477 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-81015 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/x86/amd/pmc/pmc.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/bc9aa5fe21c3966c80647ed6574b94b863f23c62 https://git.kernel.org/stable/c/30e5f4d0cd0be655c800f10ae3e530391aa6c1b5 https://git.kernel.org/stable/c/76f650a76d6a36a4bee79d94db90a0e935a95477