Sensor suspension prevention via duplicate event-enable writes
Published Sep 17, 2026 · Updated Sep 17, 2026
Runtime PM imbalance in Linux's gp2ap002 driver allows local users to prevent sensor suspension via repeated event-enable writes. The gp2ap002_write_event_config function changes the runtime PM usage count without checking whether the requested state is already active. Access requires an applicable sensor and permission to write its event-enable attribute; duplicate enables keep the sensor awake, while duplicate disables underflow the count and trigger a warning.
Summary
What happened
Runtime PM imbalance in Linux's gp2ap002 driver allows local users to prevent sensor suspension via repeated event-enable writes. The gp2ap002_write_event_config function changes the runtime PM usage count without checking whether the requested state is already active. Access requires an applicable sensor and permission to write its event-enable attribute; duplicate enables keep the sensor awake, while duplicate disables underflow the count and trigger a warning.
The record
- CVE
- CVE-2026-90249
- Published
- Sep 17, 2026
- Updated
- Sep 17, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 17, 2026CVE publishedPublication date reported by the CVE source.
- Sep 17, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=5.7
- Affected versionversion=97d642e23037c5545266f9564c9b81e6db81b122 <0fc740c25c9abb25113398ebb58e2f2ce57741a7
- Affected versionversion=97d642e23037c5545266f9564c9b81e6db81b122 <470edb012b1d9a4fba1cd59e329e60f0798c791a
- Affected versionversion=97d642e23037c5545266f9564c9b81e6db81b122 <56fe8e5f313a64e458bb6f8b982de925345e21a7
- Affected versionversion=97d642e23037c5545266f9564c9b81e6db81b122 <579c049b4cb6fc72ce2c505fc5334540be0efcd3
- Affected versionversion=97d642e23037c5545266f9564c9b81e6db81b122 <685d9d1e5c47e024413981fb7eddab86132b04a1
- Affected versionversion=97d642e23037c5545266f9564c9b81e6db81b122 <70b9482926ca92862460e659f5e5fde99ae0b4fa
- Affected versionversion=97d642e23037c5545266f9564c9b81e6db81b122 <8e76ab81319858736ccf23141e9415f9a1869337
- Affected versionversion=97d642e23037c5545266f9564c9b81e6db81b122 <b2d7a97d75b648a643f60d77f4d6d70161268855
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started