Executive Summary

This vulnerability exists in the Linux kernel's iio gyro driver for the mpu3050-core. The issue is that the function pm_runtime_get_sync() is called without checking its return value, which means the driver might try to access hardware that failed to resume properly. Additionally, the device usage count is incremented unconditionally, even if resuming the device fails. The fix involves using pm_runtime_resume_and_get(), which correctly propagates errors and prevents incrementing the usage count if the resume operation fails. Also, in the preenable phase, pm_runtime_put_autosuspend() is added on failure of set_8khz_samplerate() to handle cases where postdisable does not run.

Useful 0 Not Useful 0

Impact Analysis

If the driver accesses hardware that failed to resume due to unchecked return values, it could lead to undefined behavior, potential system instability, or hardware malfunction. Incrementing the device usage count incorrectly might prevent proper power management, causing increased power consumption or resource leaks.

Useful 0 Not Useful 0

Mitigation Strategies

The vulnerability is fixed by updating the Linux kernel to a version where the iio: gyro: mpu3050-core driver uses pm_runtime_resume_and_get() instead of pm_runtime_get_sync(), which properly handles errors and avoids incrementing the device usage count on failure.

Therefore, the immediate mitigation step is to apply the kernel update that includes this fix.

Useful 0 Not Useful 0