Suspend prevention via leaked GPIO power reference
Published Oct 18, 2026 · Updated Oct 18, 2026
A reference leak in Linux's Zynq GPIO driver allows attackers to prevent controller runtime suspend through a failed GPIO request. zynq_gpio_request() returns a pm_runtime_get_sync() error without releasing its usage reference, and gpiolib skips the matching free callback. Triggering requires an affected controller and a runtime-resume failure; the clock remains enabled, but attacker control over that failure is not established.
Summary
What happened
A reference leak in Linux's Zynq GPIO driver allows attackers to prevent controller runtime suspend through a failed GPIO request. zynq_gpio_request() returns a pm_runtime_get_sync() error without releasing its usage reference, and gpiolib skips the matching free callback. Triggering requires an affected controller and a runtime-resume failure; the clock remains enabled, but attacker control over that failure is not established.
The record
- CVE
- CVE-2026-98527
- Published
- Oct 18, 2026
- Updated
- Oct 18, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Oct 18, 2026CVE publishedPublication date reported by the CVE source.
- Oct 18, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=3.17
- Affected versionversion=3242ba117e9bd29eb748afd6f6fbfbd6dd7cfe52 <25c08be2a5e7715f19a6e02bbe9b0e5f01c77aac
- Affected versionversion=3242ba117e9bd29eb748afd6f6fbfbd6dd7cfe52 <58a417a19d80141fff3abe6004e2e47285506e73
- Affected versionversion=3242ba117e9bd29eb748afd6f6fbfbd6dd7cfe52 <60a76cdd92e25f576dc58d756a565760dde1f7a1
- Affected versionversion=3242ba117e9bd29eb748afd6f6fbfbd6dd7cfe52 <6e05f1c614a57a5d4c364dd12e20c6fd012f9d3e
- Affected versionversion=3242ba117e9bd29eb748afd6f6fbfbd6dd7cfe52 <6e20dabffbcd7b222d8e7bb85a7d8e8325df7699
- Affected versionversion=3242ba117e9bd29eb748afd6f6fbfbd6dd7cfe52 <a3e9b7f7c9558f8c9592f8f817557bff98707bb3
- Affected versionversion=3242ba117e9bd29eb748afd6f6fbfbd6dd7cfe52 <e380fba02908b809f5bbef371259003cf5887bb4
- Affected versionversion=3242ba117e9bd29eb748afd6f6fbfbd6dd7cfe52 <e9438ab5328a177c9c0e5df87eb92a7162841e98
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started