CVE-2026-31761: iio: gyro: mpu3050: Move iio_device_register() to correct location

Published May 1, 2026
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

iio: gyro: mpu3050: Move iiodeviceregister() to correct location

iiodeviceregister() should be at the end of the probe function to prevent race conditions.

Place iiodeviceregister() at the end of the probe function and place iiodeviceunregister() accordingly.

Affected Software

14 affected components
Linux Linux kernel (iio: gyro: mpu3050 driver)
Linux Linux kernel>=4.10<5.10.253
Linux Linux kernel>=5.11<5.15.203
Linux Linux kernel>=5.16<6.1.168
Linux Linux kernel>=6.2<6.6.134
Linux Linux kernel>=6.7<6.12.81
Linux Linux kernel>=6.13<6.18.22
Linux Linux kernel>=6.19<6.19.12
Linux Linux kernel=7.0-rc1
Linux Linux kernel=7.0-rc2
Linux Linux kernel=7.0-rc3
Linux Linux kernel=7.0-rc4
Linux Linux kernel=7.0-rc5
Linux Linux kernel=7.0-rc6

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Configuration

    In the mpu3050 IIO gyro probe function, move the iio_device_register() call to the end of the probe function to prevent race conditions; place iio_device_unregister() accordingly.

    Linux kernel (IIO gyro driver: mpu3050) iio_device_register() call placement = Move iio_device_register() to the end of the probe function (and ensure iio_device_unregister() is placed accordingly)

Event History

May 1, 2026
CVE Published
via MITRE·02:14 PM
Data Sourced
via MITRE·02:14 PM
DescriptionSeverity
Data Sourced
via NVD·03:16 PM
RemedyDescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

Who is exposed to this issue?

Systems running the Linux kernel with the iio: gyro: mpu3050 driver are in scope. The issue is in that driver’s probe-time device registration sequence.

2

What level of access does an attacker need?

The CVSS vector indicates local access and low privileges are required. No user interaction is required.

3

What is the potential impact if exploited?

The issue is rated high severity with a CVSS 3.1 score of 7.8. The vector indicates high impact to confidentiality, integrity, and availability.

4

What change addresses the race condition?

The fix moves iio_device_register() to the end of the driver probe function and places iio_device_unregister() accordingly, preventing registration before probe initialization is complete.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203