Skip to main content

In the Linux kernel, the following vulnerability has been resolved: platform/x86/amd/pmc: Fix LPS0 and debugfs leaks when STB init fails… (CVE-2026-81015)

0
Medium
Published: 09/11/2026 (09/11/2026, 21:31:24 UTC)
Source: GCVE Database

Description

A vulnerability in the Linux kernel's AMD platform driver (amd_pmc) was fixed to address resource leaks and list corruption when the STB initialization fails during probe. The issue caused stale registrations and leaked debugfs directories, leading to kernel list corruption and potential kernel bugs on module reload or s2idle transitions.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 09/12/2026, 01:20:43 UTC

Technical Analysis

The vulnerability occurs in the amd_pmc_probe() function of the Linux kernel where the LPS0 s2idle handler is registered and a debugfs directory is created before the final initialization step amd_stb_s2d_init(). If amd_stb_s2d_init() fails, the error path does not properly unregister the LPS0 device or remove the debugfs directory, causing resource leaks and leaving stale entries in the global lps0_s2idle_devops_head list. This stale state leads to list corruption and kernel BUGs upon module reload, and stale registrations cause s2idle transitions to call into torn-down driver state. The fix involves unwinding the debugfs directory and unregistering the LPS0 device unconditionally on failure, preventing leaks and list corruption.

Potential Impact

The vulnerability can cause kernel list corruption and kernel BUGs during module reload, potentially leading to system instability or crashes. Additionally, stale registrations cause s2idle transitions to reference invalid driver state, which may affect system power management behavior. There is no indication of direct privilege escalation or remote code execution from the provided data.

Mitigation Recommendations

A fix is available that properly cleans up the LPS0 registration and debugfs directory on failure of amd_stb_s2d_init() during probe. Users should apply the updated Linux kernel version containing this fix. No other mitigation steps are indicated or necessary.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Gcve Source
db.gcve.eu
Osv Id
GHSA-4m25-x3hr-48wm
Osv Schema Version
1.4.0
Aliases
["CVE-2026-81015"]

Threat ID: 6aa4a02855bf5e2cf5a86b1c

Added to database: 09/12/2026, 00:43:20 UTC

Last enriched: 09/12/2026, 01:20:43 UTC

Last updated: 09/12/2026, 01:20:43 UTC

Views: 3

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses