CVE-2026-98527: Linux kernel · gpio: zynq: fix runtime PM leak on request error path
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in e9438ab5328a177c9c0e5df87eb92a7162841e98 : update Linux kernel when convenient.
Data as of 26 Oct 2026, 13:47 UTC
Rated Low by Threat Radar's AI analysis · CVSS not yet scored by NVD
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 12% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in e9438ab5328a177c9c0e5df87eb92a7162841e98, e380fba02908b809f5bbef371259003cf5887bb4, a3e9b7f7c9558f8c9592f8f817557bff98707bb3 +5
Exploitation evidence
Disclosed: evidence found.
CVE published 18 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
AI-suggested
This issue has been fixed in the Linux kernel. Users should apply the official patches or upgrade to a fixed kernel version containing the commit hashes listed in the established facts. No additional mitigation is required once the fix is applied.
Description
A vulnerability in the Linux kernel's gpio driver for Zynq devices causes a runtime power management (PM) reference leak when an error occurs during GPIO request. This leak prevents the controller from runtime-suspending, leaving its clock enabled unnecessarily. The issue arises because pm_runtime_get_sync() increments the usage counter even on failure, and the error path does not properly decrement it. The fix involves switching to pm_runtime_resume_and_get(), which increments the usage counter only on success.
References
- git.kernel.org/stable/c/e380fba02908b809f5bbef371259003cf5887bb4 (opens in a new tab)
- git.kernel.org/stable/c/a3e9b7f7c9558f8c9592f8f817557bff98707bb3 (opens in a new tab)
- git.kernel.org/stable/c/60a76cdd92e25f576dc58d756a565760dde1f7a1 (opens in a new tab)
- git.kernel.org/stable/c/25c08be2a5e7715f19a6e02bbe9b0e5f01c77aac (opens in a new tab)
- git.kernel.org/stable/c/6e05f1c614a57a5d4c364dd12e20c6fd012f9d3e (opens in a new tab)
- git.kernel.org/stable/c/58a417a19d80141fff3abe6004e2e47285506e73 (opens in a new tab)
- git.kernel.org/stable/c/6e20dabffbcd7b222d8e7bb85a7d8e8325df7699 (opens in a new tab)
- git.kernel.org/stable/c/e9438ab5328a177c9c0e5df87eb92a7162841e98 (opens in a new tab)