CVE-2026-81015

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> platform/x86/amd/pmc: Fix LPS0 and debugfs leaks when STB init fails<br /> <br /> amd_pmc_probe() registers the LPS0 s2idle handler with<br /> acpi_register_lps0_dev() and creates the driver&amp;#39;s debugfs directory before<br /> calling amd_stb_s2d_init(), which is the last step in probe that can fail.<br /> <br /> When amd_stb_s2d_init() fails (for example the S2D telemetry region cannot<br /> be ioremapped on a long-running system, or the SMU rejects the S2D setup)<br /> the error path only calls pci_dev_put() and returns. This leaves<br /> amd_pmc_s2idle_dev_ops on the global lps0_s2idle_devops_head list and leaks<br /> the debugfs directory, while the devm-managed resources backing the handler<br /> are torn down.<br /> <br /> Reloading the module then walks the corrupted list in<br /> acpi_register_lps0_dev() and hits:<br /> <br /> list_add corruption. next-&gt;prev should be prev, but was NULL.<br /> kernel BUG at lib/list_debug.c:29!<br /> acpi_register_lps0_dev+0x44/0x80<br /> amd_pmc_probe+0x224/0x380 [amd_pmc]<br /> platform_probe+0x67/0x90<br /> <br /> Even without a reload, the stale registration means the next s2idle<br /> transition calls into torn-down driver state.<br /> <br /> Unwind the debugfs directory and the LPS0 registration on the<br /> amd_stb_s2d_init() error path. acpi_unregister_lps0_dev() is safe to call<br /> unconditionally here: it is guarded on the same conditions as<br /> acpi_register_lps0_dev(), which is exactly what amd_pmc_remove() already<br /> relies on.