{"api_version":"1","generated_at":"2026-09-13T13:44:41+00:00","cve":"CVE-2026-81015","urls":{"html":"https://cve.report/CVE-2026-81015","api":"https://cve.report/api/cve/CVE-2026-81015.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-81015","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-81015"},"summary":{"title":"platform/x86/amd/pmc: Fix LPS0 and debugfs leaks when STB init fails","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nplatform/x86/amd/pmc: Fix LPS0 and debugfs leaks when STB init fails\n\namd_pmc_probe() registers the LPS0 s2idle handler with\nacpi_register_lps0_dev() and creates the driver's debugfs directory before\ncalling amd_stb_s2d_init(), which is the last step in probe that can fail.\n\nWhen amd_stb_s2d_init() fails (for example the S2D telemetry region cannot\nbe ioremapped on a long-running system, or the SMU rejects the S2D setup)\nthe error path only calls pci_dev_put() and returns.  This leaves\namd_pmc_s2idle_dev_ops on the global lps0_s2idle_devops_head list and leaks\nthe debugfs directory, while the devm-managed resources backing the handler\nare torn down.\n\nReloading the module then walks the corrupted list in\nacpi_register_lps0_dev() and hits:\n\n  list_add corruption. next->prev should be prev, but was NULL.\n  kernel BUG at lib/list_debug.c:29!\n   acpi_register_lps0_dev+0x44/0x80\n   amd_pmc_probe+0x224/0x380 [amd_pmc]\n   platform_probe+0x67/0x90\n\nEven without a reload, the stale registration means the next s2idle\ntransition calls into torn-down driver state.\n\nUnwind the debugfs directory and the LPS0 registration on the\namd_stb_s2d_init() error path.  acpi_unregister_lps0_dev() is safe to call\nunconditionally here: it is guarded on the same conditions as\nacpi_register_lps0_dev(), which is exactly what amd_pmc_remove() already\nrelies on.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-09-11 20:19:10","updated_at":"2026-09-13 07:17:07"},"problem_types":[],"metrics":[{"version":"3.1","source":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","type":"Secondary","score":"7.8","severity":"HIGH","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","data":{"version":"3.1","vectorString":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","baseScore":7.8,"baseSeverity":"HIGH","attackVector":"LOCAL","attackComplexity":"LOW","privilegesRequired":"LOW","userInteraction":"NONE","scope":"UNCHANGED","confidentialityImpact":"HIGH","integrityImpact":"HIGH","availabilityImpact":"HIGH"}},{"version":"3.1","source":"CNA","type":"DECLARED","score":"7.8","severity":"HIGH","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","data":{"baseScore":7.8,"baseSeverity":"HIGH","vectorString":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"}}],"references":[{"url":"https://git.kernel.org/stable/c/30e5f4d0cd0be655c800f10ae3e530391aa6c1b5","name":"https://git.kernel.org/stable/c/30e5f4d0cd0be655c800f10ae3e530391aa6c1b5","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/bc9aa5fe21c3966c80647ed6574b94b863f23c62","name":"https://git.kernel.org/stable/c/bc9aa5fe21c3966c80647ed6574b94b863f23c62","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/76f650a76d6a36a4bee79d94db90a0e935a95477","name":"https://git.kernel.org/stable/c/76f650a76d6a36a4bee79d94db90a0e935a95477","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-81015","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-81015","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 83ad6974dd3bf34c080b3c08d36d02ebc3bd6da8 bc9aa5fe21c3966c80647ed6574b94b863f23c62 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 83ad6974dd3bf34c080b3c08d36d02ebc3bd6da8 30e5f4d0cd0be655c800f10ae3e530391aa6c1b5 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 83ad6974dd3bf34c080b3c08d36d02ebc3bd6da8 76f650a76d6a36a4bee79d94db90a0e935a95477 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6.14","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.14 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.18.50 6.18.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.2.4 7.2.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.3-rc1 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":{"cve_year":"2026","cve_id":"81015","cve":"CVE-2026-81015","epss":"0.001980000","percentile":"0.097050000","score_date":"2026-09-12","updated_at":"2026-09-13 00:08:17"},"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["drivers/platform/x86/amd/pmc/pmc.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"bc9aa5fe21c3966c80647ed6574b94b863f23c62","status":"affected","version":"83ad6974dd3bf34c080b3c08d36d02ebc3bd6da8","versionType":"git"},{"lessThan":"30e5f4d0cd0be655c800f10ae3e530391aa6c1b5","status":"affected","version":"83ad6974dd3bf34c080b3c08d36d02ebc3bd6da8","versionType":"git"},{"lessThan":"76f650a76d6a36a4bee79d94db90a0e935a95477","status":"affected","version":"83ad6974dd3bf34c080b3c08d36d02ebc3bd6da8","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["drivers/platform/x86/amd/pmc/pmc.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"6.14"},{"lessThan":"6.14","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"6.18.*","status":"unaffected","version":"6.18.50","versionType":"semver"},{"lessThanOrEqual":"7.2.*","status":"unaffected","version":"7.2.4","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.3-rc1","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.18.50","versionStartIncluding":"6.14","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.2.4","versionStartIncluding":"6.14","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.3-rc1","versionStartIncluding":"6.14","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\nplatform/x86/amd/pmc: Fix LPS0 and debugfs leaks when STB init fails\n\namd_pmc_probe() registers the LPS0 s2idle handler with\nacpi_register_lps0_dev() and creates the driver's debugfs directory before\ncalling amd_stb_s2d_init(), which is the last step in probe that can fail.\n\nWhen amd_stb_s2d_init() fails (for example the S2D telemetry region cannot\nbe ioremapped on a long-running system, or the SMU rejects the S2D setup)\nthe error path only calls pci_dev_put() and returns.  This leaves\namd_pmc_s2idle_dev_ops on the global lps0_s2idle_devops_head list and leaks\nthe debugfs directory, while the devm-managed resources backing the handler\nare torn down.\n\nReloading the module then walks the corrupted list in\nacpi_register_lps0_dev() and hits:\n\n  list_add corruption. next->prev should be prev, but was NULL.\n  kernel BUG at lib/list_debug.c:29!\n   acpi_register_lps0_dev+0x44/0x80\n   amd_pmc_probe+0x224/0x380 [amd_pmc]\n   platform_probe+0x67/0x90\n\nEven without a reload, the stale registration means the next s2idle\ntransition calls into torn-down driver state.\n\nUnwind the debugfs directory and the LPS0 registration on the\namd_stb_s2d_init() error path.  acpi_unregister_lps0_dev() is safe to call\nunconditionally here: it is guarded on the same conditions as\nacpi_register_lps0_dev(), which is exactly what amd_pmc_remove() already\nrelies on."}],"metrics":[{"cvssV3_1":{"baseScore":7.8,"baseSeverity":"HIGH","vectorString":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"scenarios":[{"lang":"en","value":"AV:L - The flaw is in amd_pmc_probe() and the ACPI LPS0 s2idle callbacks on local AMD Ryzen platforms; there is no network, Bluetooth, or remote packet path into this platform driver.\nAC:L - Once amd_stb_s2d_init() fails, the leaked LPS0 registration is deterministic; suspend then invokes the dangling handler, and a later bind or module reload list_add()s onto the already-linked or freed lps0_s2idle_devops_head node with no race the attacker must win.\nPR:L - After the probe error path leaves amd_pmc_s2idle_dev_ops on the global LPS0 list, an unprivileged local-session user on AMD laptops can trigger s2idle via logind, idle-timeout, or lid-close without init-namespace root; user namespaces cannot reach this driver.\nUI:N - Exploitation needs no separate victim action such as mounting a filesystem or opening a device; the attacker requests suspend themselves, or automatic s2idle and driver reload/bind exercise the stale list unattended.\nS:U - The dangling LPS0 list node, use of torn-down ioremap/mutex state, and kernel list corruption remain in the host kernel; this is standard kernel memory corruption, not a VM escape, IOMMU bypass, or sandbox boundary crossing.\nC:H - The stale acpi_s2idle_dev_ops stays on lps0_s2idle_devops_head after devm ioremap is torn down and after rmmod the ops object itself is freed; s2idle and list_add then read recycled vmalloc/module memory, a use-after-free disclosure primitive.\nI:H - Module reload list_add() writes through dangling next/prev pointers, and s2idle handlers issue MMIO writes and call prepare/check/restore through torn-down or freed module state, enabling control-flow hijack per kernel UAF guidance.\nA:H - Reloading amd_pmc hits list_add corruption and kernel BUG in acpi_register_lps0_dev(), and the next s2idle transition oopses or hangs while walking the corrupted list or invoking the torn-down LPS0 handler."}]}],"providerMetadata":{"dateUpdated":"2026-09-13T06:29:17.255Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/bc9aa5fe21c3966c80647ed6574b94b863f23c62"},{"url":"https://git.kernel.org/stable/c/30e5f4d0cd0be655c800f10ae3e530391aa6c1b5"},{"url":"https://git.kernel.org/stable/c/76f650a76d6a36a4bee79d94db90a0e935a95477"}],"title":"platform/x86/amd/pmc: Fix LPS0 and debugfs leaks when STB init fails","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-81015","datePublished":"2026-09-11T19:43:04.063Z","dateReserved":"2026-08-26T14:34:25.813Z","dateUpdated":"2026-09-13T06:29:17.255Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-09-11 20:19:10","lastModifiedDate":"2026-09-13 07:17:07","problem_types":[],"metrics":{"cvssMetricV31":[{"source":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","type":"Secondary","cvssData":{"version":"3.1","vectorString":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","baseScore":7.8,"baseSeverity":"HIGH","attackVector":"LOCAL","attackComplexity":"LOW","privilegesRequired":"LOW","userInteraction":"NONE","scope":"UNCHANGED","confidentialityImpact":"HIGH","integrityImpact":"HIGH","availabilityImpact":"HIGH"},"exploitabilityScore":1.8,"impactScore":5.9}]},"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"81015","Ordinal":"1","Title":"platform/x86/amd/pmc: Fix LPS0 and debugfs leaks when STB init f","CVE":"CVE-2026-81015","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"81015","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\nplatform/x86/amd/pmc: Fix LPS0 and debugfs leaks when STB init fails\n\namd_pmc_probe() registers the LPS0 s2idle handler with\nacpi_register_lps0_dev() and creates the driver's debugfs directory before\ncalling amd_stb_s2d_init(), which is the last step in probe that can fail.\n\nWhen amd_stb_s2d_init() fails (for example the S2D telemetry region cannot\nbe ioremapped on a long-running system, or the SMU rejects the S2D setup)\nthe error path only calls pci_dev_put() and returns.  This leaves\namd_pmc_s2idle_dev_ops on the global lps0_s2idle_devops_head list and leaks\nthe debugfs directory, while the devm-managed resources backing the handler\nare torn down.\n\nReloading the module then walks the corrupted list in\nacpi_register_lps0_dev() and hits:\n\n  list_add corruption. next->prev should be prev, but was NULL.\n  kernel BUG at lib/list_debug.c:29!\n   acpi_register_lps0_dev+0x44/0x80\n   amd_pmc_probe+0x224/0x380 [amd_pmc]\n   platform_probe+0x67/0x90\n\nEven without a reload, the stale registration means the next s2idle\ntransition calls into torn-down driver state.\n\nUnwind the debugfs directory and the LPS0 registration on the\namd_stb_s2d_init() error path.  acpi_unregister_lps0_dev() is safe to call\nunconditionally here: it is guarded on the same conditions as\nacpi_register_lps0_dev(), which is exactly what amd_pmc_remove() already\nrelies on.","Type":"Description","Title":"platform/x86/amd/pmc: Fix LPS0 and debugfs leaks when STB init f"}]}}}