Skip to main content
VulnerabilityPublished

CVE-2026-98527: Linux kernel · gpio: zynq: fix runtime PM leak on request error path

Source GCVE Database

0
Authoritative record:CVE-2026-98527· Low

Not known to be exploited · fixed in e9438ab5328a177c9c0e5df87eb92a7162841e98 : update Linux kernel when convenient.

Data as of 26 Oct 2026, 13:47 UTC

Severity
Low

Rated by Threat Radar · 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

  1. Disclosed: evidence found.

    CVE published 18 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 3242ba117e9bd29eb748afd6f6fbfbd6dd7cfe52, < e9438ab5328a177c9c0e5df87eb92a7162841e98
Fixed in
  • e9438ab5328a177c9c0e5df87eb92a7162841e98
LinuxLinuxAffected
  • ≥ 3242ba117e9bd29eb748afd6f6fbfbd6dd7cfe52, < e380fba02908b809f5bbef371259003cf5887bb4
Fixed in
  • e380fba02908b809f5bbef371259003cf5887bb4
LinuxLinuxAffected
  • ≥ 3242ba117e9bd29eb748afd6f6fbfbd6dd7cfe52, < a3e9b7f7c9558f8c9592f8f817557bff98707bb3
Fixed in
  • a3e9b7f7c9558f8c9592f8f817557bff98707bb3
LinuxLinuxAffected
  • ≥ 3242ba117e9bd29eb748afd6f6fbfbd6dd7cfe52, < 60a76cdd92e25f576dc58d756a565760dde1f7a1
Fixed in
  • 60a76cdd92e25f576dc58d756a565760dde1f7a1
LinuxLinuxAffected
  • ≥ 3242ba117e9bd29eb748afd6f6fbfbd6dd7cfe52, < 58a417a19d80141fff3abe6004e2e47285506e73
Fixed in
  • 58a417a19d80141fff3abe6004e2e47285506e73
LinuxLinuxAffected
  • ≥ 3242ba117e9bd29eb748afd6f6fbfbd6dd7cfe52, < 25c08be2a5e7715f19a6e02bbe9b0e5f01c77aac
Fixed in
  • 25c08be2a5e7715f19a6e02bbe9b0e5f01c77aac

AI-suggested

A fix is available that replaces pm_runtime_get_sync() with pm_runtime_resume_and_get() in the Zynq gpio driver to prevent the runtime PM usage counter leak. Users should apply the official Linux kernel update that includes this fix. No additional mitigation is indicated.

Description

A vulnerability in the Linux kernel's gpio driver for the Zynq platform causes a runtime power management (PM) usage counter leak when pm_runtime_get_sync() fails during gpio request. This leak prevents the controller from runtime-suspending, leaving its clock enabled unnecessarily. The issue is fixed by switching to pm_runtime_resume_and_get(), which increments the usage counter only on success.

References

Community reviews

Loading reviews…