iio MPU3050 Registration Race

Vulnerability analysis

Root Cause: The iio_device_register() function was called too early in the probe function, before all device initialization was complete. This created a race condition where userspace could access the device through the IIO subsystem before the driver had finished setting up interrupts, power management, and other critical resources.

Attack Surface: Local access required. The vulnerability affects the MPU-3050 gyroscope driver initialization sequence. An attacker would need local access to trigger device probing (e.g., through device hotplug or module loading) and attempt to access the IIO device interface during the narrow race window.

Fix Mechanism: The patch moves iio_device_register() to the very end of the probe function, after all initialization is complete including IRQ setup and power management configuration. It also reorders iio_device_unregister() to be called first in the remove function to maintain proper cleanup ordering.