CVE-2026-99049: Linux kernel · gpio: xilinx: fix runtime PM leak on request error path
Source GCVE Database
Not known to be exploited · fixed in ff82fc3a4a1d417dee1229681cc5285986edb1fa : update Linux kernel when convenient.
Data as of 26 Oct 2026, 12:55 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 6% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in ff82fc3a4a1d417dee1229681cc5285986edb1fa, f73ee2bd2293f8cc340061c5229395ace71fc2eb, b07b3925f676640103b3d74b93fc401b1c873d13 +2
Exploitation evidence
Disclosed: evidence found.
CVE published 23 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– |
Description
In the Linux kernel, the following vulnerability has been resolved: gpio: xilinx: fix runtime PM leak on request error path pm_runtime_get_sync() leaves the usage counter incremented even when it fails, and xgpio_request() returns the error without dropping it. gpiolib does not call ->free() when ->request() fails, so xgpio_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.
References
- nvd.nist.gov/vuln/detail/CVE-2026-99049 (opens in a new tab)
- git.kernel.org/stable/c/2fd6ecda5d1f47cffcfadddb35ee49402162c724 (opens in a new tab)
- git.kernel.org/stable/c/a027e0d7765d1531ee39e4dae81951b04f32ba7b (opens in a new tab)
- git.kernel.org/stable/c/b07b3925f676640103b3d74b93fc401b1c873d13 (opens in a new tab)
- git.kernel.org/stable/c/f73ee2bd2293f8cc340061c5229395ace71fc2eb (opens in a new tab)
- git.kernel.org/stable/c/ff82fc3a4a1d417dee1229681cc5285986edb1fa (opens in a new tab)