In the Linux kernel, the following vulnerability has been resolved: gpio: xilinx: fix runtime PM leak on request error path pm_runtime_get_sync()… (CVE-2026-99049)
Description
A vulnerability in the Linux kernel's Xilinx GPIO driver caused a runtime PM (power management) leak on the request error path. The issue arises because pm_runtime_get_sync() increments the usage counter even on failure, and the error path does not properly decrement it, leading to a leaked reference. This prevents the controller from runtime-suspending and keeps its clock enabled unnecessarily. The fix involves switching to pm_runtime_resume_and_get(), which increments the usage counter only on success.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Linux kernel's Xilinx GPIO driver had a flaw where pm_runtime_get_sync() would increment the runtime PM usage counter even if it failed, and the xgpio_request() function would return the error without decrementing the counter. Since the gpiolib does not call the free function on request failure, the corresponding pm_runtime_put() call in xgpio_free() never occurs, causing a reference leak. This leak prevents the controller from runtime-suspending, leaving its clock enabled and potentially wasting power. The vulnerability was resolved by changing the code to use pm_runtime_resume_and_get(), which increments the usage counter only upon success, preventing the leak.
Potential Impact
The vulnerability causes a runtime power management reference leak in the Xilinx GPIO driver, which prevents the controller from entering runtime suspend state. This results in the controller's clock remaining enabled unnecessarily, potentially leading to increased power consumption. There is no indication of direct security compromise or code execution impact.
Mitigation Recommendations
A fix is available that changes the driver to use pm_runtime_resume_and_get() instead of pm_runtime_get_sync() to avoid incrementing the usage counter on failure. Users should apply the official Linux kernel patch that addresses this issue. Since this is a kernel-level fix, updating to the patched kernel version is the recommended remediation.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-gqf7-c35f-5xh6
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-99049"]
Threat ID: 6adbaaced73cc49347b2051e
Added to database: 10/23/2026, 18:43:26 UTC
Last enriched: 10/23/2026, 18:52:11 UTC
Last updated: 10/24/2026, 00:25:10 UTC
Views: 6
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
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
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.