---
id: "CVE-2026-98527"
kind: "vulnerability"
aliases: ["CVE-2026-98527"]
title: "Linux kernel Zynq GPIO driver leaks runtime PM reference on request error"
severity: "low"
cvss: null
epss: null
exploited: false
status: "open"
category: "runtime"
products: []
ecosystems: []
tags: ["gpio", "linux-kernel", "runtime", "zynq"]
not_affected_if: []
published_at: "2026-10-18T16:17:04+00:00"
first_seen_at: "2026-10-23T21:57:15+00:00"
updated_at: "2026-10-25T05:25:06+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-98527", "first_seen_at": "2026-10-23T21:57:15+00:00"}]
---

# Linux kernel Zynq GPIO driver leaks runtime PM reference on request error

The Zynq GPIO driver in the Linux kernel leaks a runtime power-management reference when a GPIO request fails, because the error path does not drop the usage counter. As a result the controller cannot runtime-suspend and its clock stays enabled.

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

## Timeline

- 2026-10-23T21:57:15+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-98527

## From the sources

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

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

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

gpiolib does not call ->free() when ->request() fails, so zynq_gpio_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_