# CVE-2026-99049: gpio: xilinx: fix runtime PM leak on request error path


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 23 Oct 2026
- **Updated:** 23 Oct 2026
- **Also known as:** AZL-110927, BELL-CVE-2026-99049, DEBIAN-CVE-2026-99049, GHSA-gqf7-c35f-5xh6, UBUNTU-CVE-2026-99049

## What is CVE-2026-99049?

CVE-2026-99049 is a vulnerability in Linux, published on 23 Oct 2026. 

### Official 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.

## Which versions are affected by CVE-2026-99049?


## How do I fix CVE-2026-99049?

Upgrade to a fixed version.

## Is CVE-2026-99049 being exploited?

There is no known exploitation of CVE-2026-99049 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-99049 and fix it if it is affected.

What it is: CVE-2026-99049 is a vulnerability in Linux, published on 23 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-99049 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-99049/ (Markdown: https://insights.sbomify.com/CVE-2026-99049/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-99049
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-99049
- OSV: https://osv.dev/vulnerability/CVE-2026-99049

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-99049/
Summaries are generated and may contain mistakes; the official description above is the record.