Linux Kernel up to 7.2.5 gp2ap002 write_event_config multiple operations on resource in single-operation context

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.2 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Linux Kernel up to 7.2.5. It has been rated as problematic. Affected by this vulnerability is the function write_event_config of the component gp2ap002. Performing a manipulation results in multiple operations on resource in single-operation context.
This vulnerability is identified as CVE-2026-90249. The attack is only possible with local access. There is not any exploit available.
Upgrading the affected component is advised.
Details
A vulnerability classified as problematic has been found in Linux Kernel up to 7.2.5. This affects the function write_event_config of the component gp2ap002. The manipulation with an unknown input leads to a multiple operations on resource in single-operation context vulnerability. CWE is classifying the issue as CWE-675. The product performs the same operation on a resource two or more times, when the operation should only be applied once. This is going to have an impact on availability. The summary by CVE is:
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.
It is possible to read the advisory at git.kernel.org. This vulnerability is uniquely identified as CVE-2026-90249 since 09/11/2026. The exploitability is told to be easy. Attacking locally is a requirement. The exploitation needs additional levels of successful authentication. Technical details of the vulnerability are known, but there is no available exploit.
Upgrading to version 5.10.270, 5.15.221, 6.1.188, 6.6.157, 6.12.110, 6.18.52, 7.2.6 or 7.3-rc1 eliminates this vulnerability. Applying the patch b2d7a97d75b648a643f60d77f4d6d70161268855/685d9d1e5c47e024413981fb7eddab86132b04a1/56fe8e5f313a64e458bb6f8b982de925345e21a7/8e76ab81319858736ccf23141e9415f9a1869337/70b9482926ca92862460e659f5e5fde99ae0b4fa/0fc740c25c9abb25113398ebb58e2f2ce57741a7/470edb012b1d9a4fba1cd59e329e60f0798c791a/579c049b4cb6fc72ce2c505fc5334540be0efcd3 is able to eliminate this problem. The best possible mitigation is suggested to be upgrading to the latest version.
Be aware that VulDB is the high quality source for vulnerability data.
Product
Type
Vendor
Name
Version
- 5.10.269
- 5.15.220
- 6.1.187
- 6.6.156
- 6.12.109
- 6.18.0
- 6.18.1
- 6.18.2
- 6.18.3
- 6.18.4
- 6.18.5
- 6.18.6
- 6.18.7
- 6.18.8
- 6.18.9
- 6.18.10
- 6.18.11
- 6.18.12
- 6.18.13
- 6.18.14
- 6.18.15
- 6.18.16
- 6.18.17
- 6.18.18
- 6.18.19
- 6.18.20
- 6.18.21
- 6.18.22
- 6.18.23
- 6.18.24
- 6.18.25
- 6.18.26
- 6.18.27
- 6.18.28
- 6.18.29
- 6.18.30
- 6.18.31
- 6.18.32
- 6.18.33
- 6.18.34
- 6.18.35
- 6.18.36
- 6.18.37
- 6.18.38
- 6.18.39
- 6.18.40
- 6.18.41
- 6.18.42
- 6.18.43
- 6.18.44
- 6.18.45
- 6.18.46
- 6.18.47
- 6.18.48
- 6.18.49
- 6.18.50
- 6.18.51
- 7.2.0
- 7.2.1
- 7.2.2
- 7.2.3
- 7.2.4
- 7.2.5
License
Website
- Vendor: https://www.kernel.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.4VulDB Meta Temp Score: 4.2
VulDB Base Score: 4.4
VulDB Temp Score: 4.2
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Multiple operations on resource in single-operation contextCWE: CWE-675
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: No
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Kernel 5.10.270/5.15.221/6.1.188/6.6.157/6.12.110/6.18.52/7.2.6/7.3-rc1
Patch: b2d7a97d75b648a643f60d77f4d6d70161268855/685d9d1e5c47e024413981fb7eddab86132b04a1/56fe8e5f313a64e458bb6f8b982de925345e21a7/8e76ab81319858736ccf23141e9415f9a1869337/70b9482926ca92862460e659f5e5fde99ae0b4fa/0fc740c25c9abb25113398ebb58e2f2ce57741a7/470edb012b1d9a4fba1cd59e329e60f0798c791a/579c049b4cb6fc72ce2c505fc5334540be0efcd3
Timeline
09/11/2026 CVE reserved09/17/2026 Advisory disclosed
09/17/2026 VulDB entry created
09/17/2026 VulDB entry last update
Sources
Vendor: kernel.orgAdvisory: git.kernel.org
Status: Confirmed
CVE: CVE-2026-90249 (🔒)
GCVE (CVE): GCVE-0-2026-90249
GCVE (VulDB): GCVE-100-406791
Entry
Created: 09/17/2026 21:11Changes: 09/17/2026 21:11 (59)
Complete: 🔍
Cache ID: 216::103
Be aware that VulDB is the high quality source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.