# CVE-2026-90249: iio: light: gp2ap002: Fix unbalanced runtime PM on repeated event writes

> Repeated writes to the gp2ap002 light sensor event attribute cause runtime PM reference leaks or underflows, preventing device suspension and triggering kernel warnings.

- **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:** 17 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-102702, BELL-CVE-2026-90249, DEBIAN-CVE-2026-90249, GHSA-cp7w-v98j-9px9, UBUNTU-CVE-2026-90249

## What is CVE-2026-90249?

CVE-2026-90249 is a denial of service vulnerability in Linux, published on 17 Sep 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 unbalanced runtime PM on repeated event writes

The IIO core does not filter duplicate writes to the event enable
attribute, so writing the same value twice invokes
write_event_config() twice. Enabling twice leaks a runtime PM
reference, preventing the device from ever suspending again;
disabling twice underflows the usage count and triggers a
"Runtime PM usage count underflow" warning.

Bail out early when the requested state matches the current state.
While at it, switch to pm_runtime_resume_and_get() so a failed
resume is propagated to userspace instead of silently marking the
event enabled.

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


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

Apply the vendor's patch.

## Is CVE-2026-90249 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-90249 is a denial of service vulnerability in Linux, published on 17 Sep 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-90249 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-90249/ (Markdown: https://insights.sbomify.com/CVE-2026-90249/index.md)
```

## Sources

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

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