---
id: "CVE-2026-99049"
kind: "vulnerability"
aliases: ["CVE-2026-99049"]
title: "Linux kernel: Xilinx GPIO error path leaks power reference, blocks suspend"
severity: "low"
cvss: null
epss: 0.00209
exploited: false
status: "open"
category: "runtime"
products: []
ecosystems: []
tags: ["embedded", "linux-kernel", "runtime", "xilinx-gpio"]
not_affected_if: ["no-xilinx-gpio-hardware"]
published_at: "2026-10-23T13:17:28+00:00"
first_seen_at: "2026-10-23T21:57:33+00:00"
updated_at: "2026-10-25T12:38:50+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-99049", "first_seen_at": "2026-10-23T21:57:33+00:00"}, {"source": "epss", "url": "https://api.first.org/data/v1/epss?cve=CVE-2026-99049", "first_seen_at": "2026-10-25T12:38:50+00:00"}]
---

# Linux kernel: Xilinx GPIO error path leaks power reference, blocks suspend

In the Linux kernel's Xilinx GPIO driver, a failed request leaves the runtime power-management usage counter raised, because the matching release never runs. The controller then cannot runtime-suspend and its clock stays enabled, which wastes power and can stall power management rather than giving an attacker code execution.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- unknown

## Fix

- Update the Linux kernel to a release that includes the upstream commit 'gpio: xilinx: fix runtime PM leak on request error path' (the fix switches to pm_runtime_resume_and_get()); exact fixed version numbers are not given in the sources.

## Timeline

- 2026-10-23T21:57:33+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-99049
- 2026-10-25T12:38:50+00:00 epss https://api.first.org/data/v1/epss?cve=CVE-2026-99049

## From the sources

In the Linux kernel, the following vulnerability has been resolved:

gpio: xilinx: fix runtime PM leak on request error path

pm_runtime_get_sync() leaves the usage counter incremented even when it
fails, and xgpio_request() returns the error without dropping it.

gpiolib does not call ->free() when ->request() fails, so xgpio_free(),
which holds the only matching pm_runtime_put(), never runs. The reference
is leaked and the controller can no longer runtime-suspend, so its clock
stays enabled.

Switch to pm_runtime_resume_and_get(), which only increments the usage
counter on success.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_