CVE-2026-81015
Received Received - Intake

Memory Leak in AMD PMC Kernel Driver

Publication date: 2026-09-11

Last updated on: 2026-09-11

Assigner: kernel.org

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-09-11
Last Modified
2026-09-11
Generated
2026-09-12
AI Q&A
2026-09-11
EPSS Evaluated
N/A
NVD
CVE-2026-81015
EUVD
EUVD-2026-76338

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
amd linux_kernel *

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability in the Linux kernel involves improper cleanup when the AMD PMC driver fails during initialization. The driver registers a sleep state handler and creates a debugfs directory before completing setup. If setup fails, these resources are not properly released, leading to corruption in the kernel's sleep state management system.

Detection Guidance

This vulnerability is specific to the Linux kernel's AMD PMC driver and may not have direct network detection methods. Check kernel logs for errors related to amd_pmc or LPS0 during system suspend/resume cycles. Commands like dmesg | grep -i amd_pmc or journalctl -k | grep -i amd_pmc may reveal issues.

Impact Analysis

This could cause system crashes during sleep transitions, kernel panics, or corruption of kernel data structures. Users might experience unexpected reboots, data loss, or system instability, particularly on long-running systems where the S2D telemetry region becomes inaccessible.

Mitigation Strategies

Update the Linux kernel to a patched version that includes the fix for CVE-2026-81015. If immediate patching is not possible, avoid using AMD systems with the affected kernel module or disable the amd_pmc driver if not required.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-81015. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart