Kernel crash via stale LPS0 registration
Published Sep 11, 2026 · Updated Sep 11, 2026
Resource cleanup error in the AMD PMC driver in Linux 6.14 allows attackers to crash the kernel via unspecified vectors. The amd_pmc_probe() failure path returns after amd_stb_s2d_init() fails without removing its debugfs directory or unregistering amd_pmc_s2idle_dev_ops, leaving callbacks backed by released resources. The condition requires an AMD PMC system where STB initialization fails; module reload or a later s2idle transition then reaches the stale state.
Summary
What happened
Resource cleanup error in the AMD PMC driver in Linux 6.14 allows attackers to crash the kernel via unspecified vectors. The amd_pmc_probe() failure path returns after amd_stb_s2d_init() fails without removing its debugfs directory or unregistering amd_pmc_s2idle_dev_ops, leaving callbacks backed by released resources. The condition requires an AMD PMC system where STB initialization fails; module reload or a later s2idle transition then reaches the stale state.
The record
- CVE
- CVE-2026-81015
- Published
- Sep 11, 2026
- Updated
- Sep 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Sep 11, 2026CVE publishedPublication date reported by the CVE source.
- Sep 11, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=6.14
- Affected versionversion=83ad6974dd3bf34c080b3c08d36d02ebc3bd6da8 <30e5f4d0cd0be655c800f10ae3e530391aa6c1b5
- Affected versionversion=83ad6974dd3bf34c080b3c08d36d02ebc3bd6da8 <76f650a76d6a36a4bee79d94db90a0e935a95477
- Affected versionversion=83ad6974dd3bf34c080b3c08d36d02ebc3bd6da8 <bc9aa5fe21c3966c80647ed6574b94b863f23c62
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo