CVE-2026-81015 (GCVE-0-2026-81015)
Vulnerability from cvelistv5 – Published: 2026-09-11 19:43 – Updated: 2026-10-19 08:46
VLAI
EPSS
VEX
Title
platform/x86/amd/pmc: Fix LPS0 and debugfs leaks when STB init fails
Summary
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.
Severity
7.8 (High)
Assigner
References
Impacted products
2 products
| Vendor | Product | Version | |
|---|---|---|---|
| Linux | Linux |
Affected:
49de59f69a76f538bfa5d0638a8c98d052546567 , < d201c09c2428a4a8fd3bdcb032ae99f1e016458c
(git)
Affected: 83ad6974dd3bf34c080b3c08d36d02ebc3bd6da8 , < bc9aa5fe21c3966c80647ed6574b94b863f23c62 (git) Affected: 83ad6974dd3bf34c080b3c08d36d02ebc3bd6da8 , < 30e5f4d0cd0be655c800f10ae3e530391aa6c1b5 (git) Affected: 83ad6974dd3bf34c080b3c08d36d02ebc3bd6da8 , < 76f650a76d6a36a4bee79d94db90a0e935a95477 (git) |
|
| Linux | Linux |
Affected:
6.14
Unaffected: 0 , < 6.14 (semver) Unaffected: 6.18.50 , ≤ 6.18.* (semver) Unaffected: 7.2.4 , ≤ 7.2.* (semver) Unaffected: 7.3 , ≤ * (original_commit_for_fix) |
{
"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": "d201c09c2428a4a8fd3bdcb032ae99f1e016458c",
"status": "affected",
"version": "49de59f69a76f538bfa5d0638a8c98d052546567",
"versionType": "git"
},
{
"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",
"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",
"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\u0027s 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-\u003eprev 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-10-19T08:46:40.596Z",
"orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"shortName": "Linux"
},
"references": [
{
"url": "https://git.kernel.org/stable/c/d201c09c2428a4a8fd3bdcb032ae99f1e016458c"
},
{
"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-10-19T08:46:40.596Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2",
"vulnerability-lookup:meta": {
"epss": {
"cve": "CVE-2026-81015",
"date": "2026-11-17",
"epss": "0.00175",
"percentile": "0.07082"
},
"nvd": {
"cve": {
"affected": [
{
"affectedData": [
{
"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": "d201c09c2428a4a8fd3bdcb032ae99f1e016458c",
"status": "affected",
"version": "49de59f69a76f538bfa5d0638a8c98d052546567",
"versionType": "git"
},
{
"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",
"versionType": "original_commit_for_fix"
}
]
}
],
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
],
"cveTags": [],
"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\u0027s 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-\u003eprev 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."
}
],
"id": "CVE-2026-81015",
"lastModified": "2026-10-19T09:17:34.923",
"metrics": {
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "LOCAL",
"availabilityImpact": "HIGH",
"baseScore": 7.8,
"baseSeverity": "HIGH",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "LOW",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
"version": "3.1"
},
"exploitabilityScore": 1.8,
"impactScore": 5.9,
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"type": "Secondary"
}
]
},
"published": "2026-09-11T20:19:10.437",
"references": [
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/30e5f4d0cd0be655c800f10ae3e530391aa6c1b5"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/76f650a76d6a36a4bee79d94db90a0e935a95477"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/bc9aa5fe21c3966c80647ed6574b94b863f23c62"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/d201c09c2428a4a8fd3bdcb032ae99f1e016458c"
}
],
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"vulnStatus": "Received"
}
},
"redhat_vex": {
"aggregate_severity": "Moderate",
"current_release_date": "2026-11-07T04:54:01+00:00",
"cve": "CVE-2026-81015",
"id": "CVE-2026-81015",
"initial_release_date": "2026-09-11T00:00:00+00:00",
"product_status:known_affected": "110",
"product_status:known_not_affected": "93",
"source": "Red Hat CSAF VEX",
"status": "final",
"title": "kernel: platform/x86/amd/pmc: Fix LPS0 and debugfs leaks when STB init fails",
"url": "https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-81015.json",
"version": "3"
},
"suse_vex": {
"aggregate_severity": "moderate",
"current_release_date": "2026-11-14T01:45:09Z",
"cve": "CVE-2026-81015",
"id": "CVE-2026-81015",
"initial_release_date": "2026-09-12T16:35:28Z",
"product_status:known_not_affected": "354",
"product_status:recommended": "92",
"source": "SUSE CSAF VEX",
"status": "interim",
"title": "SUSE CVE CVE-2026-81015",
"url": "https://ftp.suse.com/pub/projects/security/csaf-vex/2026/cve-2026-81015.json",
"version": "8"
}
}
}
Loading…
Loading…
Experimental. This forecast is provided for visualization only and may change without notice. Do not use it for operational decisions.
Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Loading…
Loading…
The MITRE ATT&CK techniques below are AI-generated suggestions, inferred from the description of the
vulnerability by the CIRCL/vulnerability-attack-technique-classification-roberta-base
model, served locally by ML-Gateway.
They have not been verified by an analyst and are provided for guidance only.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Loading…
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.
Loading…