CVE-2026-90249 Linux CVE debrief

Who should care

Defenders responsible for Linux kernel systems using the iio: light: gp2ap002 driver should assess exposure and prioritize patching. This includes operators, platform administrators, vulnerability management teams, and security teams who need to ensure that their systems are updated to prevent potential issues with device suspension and runtime PM usage count.

Why it matters

Defenders should prioritize verifying and applying patches for this vulnerability, especially for systems using the affected driver, as it can prevent the device from suspending again and potentially cause a runtime PM usage count underflow.

• Prevent device from suspending again due to unbalanced runtime PM
• Potential runtime PM usage count underflow

Technical summary

The Linux kernel has a vulnerability in the iio: light: gp2ap002 driver that can cause unbalanced runtime PM on repeated event writes. This can lead to a runtime PM usage count underflow and prevent the device from suspending again. The issue is resolved by bailing out early when the requested state matches the current state and switching to pm_runtime_resume_and_get(). This change ensures that the device's runtime PM reference count remains balanced, preventing potential issues with device suspension and runtime PM usage count.

Defensive priority

Defenders should prioritize verifying and applying patches for this vulnerability, especially for systems using the affected driver.

Recommended defensive actions

• Verify and apply patches for this vulnerability
• Review system configurations and update affected drivers
• Monitor system logs for potential issues
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
• Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed
• Check relevant monitoring, detection, and logs for exposed assets that need extra review

Evidence notes

The CVE record and source item provide details on the vulnerability, including its description and affected versions. However, the corpus does not establish specific exploitation or impact, requiring verification from official sources. Defenders should verify the vulnerability's existence and impact through official sources like the CVE Program record and NIST NVD detail page.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.