Description
In the Linux kernel, the following vulnerability has been resolved:
iio: gyro: mpu3050-core: fix pm_runtime error handling
The return value of pm_runtime_get_sync() is not checked, allowing the driver to access hardware that may fail to resume. The device usage count is also unconditionally incremented. Use pm_runtime_resume_and_get() which propagates errors and avoids incrementing the usage count on failure.
In preenable, add pm_runtime_put_autosuspend() on set_8khz_samplerate() failure since postdisable does not run when preenable fails.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:HAffected software
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= 3904b28efb2c780c23dcddfb87e07fe0230661e5, < 935f57dd43492240e1ca220dd065d624efece6be; >= 3904b28efb2c780c23dcddfb87e07fe0230661e5, < 8544c488e50206f00630a8bbba43d2c8bd290345; >= 3904b28efb2c780c23dcddfb87e07fe0230661e5, < 35f54e7bcb1eccdc6e5bff06580eeef2e0ff3677; >= 3904b28efb2c780c23dcddfb87e07fe0230661e5, < 2a86a396aa001a9f9ba2d37dda36573a76f17c90; >= 3904b28efb2c780c23dcddfb87e07fe0230661e5, < 66c0d1d600e7be034959cf49edab104cb5a39258; >= 3904b28efb2c780c23dcddfb87e07fe0230661e5, < 42685cf96e28262e0b84d74447f3d99f3f6a72e0; >= 3904b28efb2c780c23dcddfb87e07fe0230661e5, < 7a3dec5b265cf87678b10c98a72a435a8e769bb7; >= 3904b28efb2c780c23dcddfb87e07fe0230661e5, < acc3949aab3e8094641a9c7c2768de1958c88378 |
| Linux | Linux | 4.10 |
References
- https://git.kernel.org/stable/c/2a86a396aa001a9f9ba2d37dda36573a76f17c90Patch
- https://git.kernel.org/stable/c/35f54e7bcb1eccdc6e5bff06580eeef2e0ff3677Patch
- https://git.kernel.org/stable/c/42685cf96e28262e0b84d74447f3d99f3f6a72e0Patch
- https://git.kernel.org/stable/c/66c0d1d600e7be034959cf49edab104cb5a39258Patch
- https://git.kernel.org/stable/c/7a3dec5b265cf87678b10c98a72a435a8e769bb7Patch
- https://git.kernel.org/stable/c/8544c488e50206f00630a8bbba43d2c8bd290345Patch
- https://git.kernel.org/stable/c/935f57dd43492240e1ca220dd065d624efece6bePatch
- https://git.kernel.org/stable/c/acc3949aab3e8094641a9c7c2768de1958c88378Patch
Timeline
- Published
- May 8, 2026
- Last modified
- Nov 11, 2026
- NVD status
- Analyzed