# CVE-2026-64494: iio: light: gp2ap002: fix runtime PM leak on read error

> A local attacker can cause a runtime PM reference leak in the gp2ap002 light sensor driver, preventing device autosuspend and leading to resource exhaustion.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 25 Jul 2026
- **Updated:** 17 Aug 2026
- **Also known as:** BELL-CVE-2026-64494, DEBIAN-CVE-2026-64494, GHSA-gpwj-cvm7-rmhj, ROOT-OS-UBUNTU-2204-CVE-2026-64494, UBUNTU-CVE-2026-64494

## What is CVE-2026-64494?

CVE-2026-64494 is a denial of service vulnerability in Linux, published on 25 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In the Linux kernel, the following vulnerability has been resolved:

iio: light: gp2ap002: fix runtime PM leak on read error

gp2ap002_read_raw() calls pm_runtime_get_sync() before reading the
lux value, but if gp2ap002_get_lux() fails, it returns directly. This
skips the pm_runtime_put_autosuspend() call at the "out" label,
permanently leaking a runtime PM reference and preventing the device
from autosuspending.

Replace the direct return with a "goto out" to ensure the reference
is properly dropped on the error path.

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


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

Apply the vendor's patch.

## Is CVE-2026-64494 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-64494 is a denial of service vulnerability in Linux, published on 25 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-64494 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-64494/ (Markdown: https://insights.sbomify.com/CVE-2026-64494/index.md)
```

## Sources

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

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