CVE-2026-90249: iio: light: gp2ap002: Fix unbalanced runtime PM on repeated event writes
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 writeeventconfig() 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 pmruntimeresumeandget() so a failed resume is propagated to userspace instead of silently marking the event enabled.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Linux kernel IIO core (iio: light: gp2ap002)to a version that resolves this vulnerability.Patch iio: light: gp2ap002: Fix unbalanced runtime PM on repeated event writes
Event History
Frequently Asked Questions
What systems are exposed to this issue?
Systems using the Linux kernel gp2ap002 IIO light-sensor driver are exposed when software writes the driver's event-enable attribute repeatedly with the same value. The issue is tied to event configuration writes rather than ordinary sensor operation alone.
What behavior indicates that a system may be affected?
Repeatedly enabling the same event can leave an extra runtime power-management reference, causing the device to remain active instead of suspending. Repeatedly disabling the same event can trigger a "Runtime PM usage count underflow" warning.
What changes with the fix when event enabling fails?
The fix avoids duplicate state changes and uses pm_runtime_resume_and_get(). If runtime resume fails, the event-enable operation reports the failure to userspace rather than marking the event as enabled.