CVE-2026-31761: iio: gyro: mpu3050: Move iio_device_register() to correct location
In the Linux kernel, the following vulnerability has been resolved:
iio: gyro: mpu3050: Move iio_device_register() to correct location
iio_device_register() should be at the end of the probe function to
prevent race conditions.
Place iio_device_register() at the end of the probe function and place
iio_device_unregister() accordingly.
Security readout for executives and security teams
Plain-English summary
A race condition in the Linux MPU3050 gyroscope driver exposes the device interface before initialization finishes. The supplied CVSS assessment indicates that a low-privileged local attacker could potentially affect data confidentiality, integrity, and system availability. The sources do not establish remote reachability or exploitation in the wild.
Executive priority
Prioritize normal high-severity patching, especially for shared systems permitting untrusted local users or workloads. This is not supported as an internet-scale emergency because access is local and active exploitation is unconfirmed. Require owners to verify vendor kernel status rather than relying only on upstream version labels.
Technical view
The mpu3050 probe path called iio_device_register() before completing initialization, potentially exposing partially initialized state to concurrent access. Linux resolved this by moving registration to the end of probe and adjusting unregistration accordingly. The supplied CVSS v3.1 score is 7.8 with local, low-privileged, no-interaction attack requirements.
Likely exposure
Exposure is most likely on systems using affected Linux kernels where the MPU3050 IIO driver is present or usable. Exploitation requires local low-privileged access. The supplied affected-version data contains ambiguous entries and does not provide clear version ranges, so distributor-specific kernel mapping is necessary.
Exploitation context
The bundle marks this CVE as absent from KEV and provides no evidence of active exploitation, public proof-of-concept code, or observed attacks. The race is timing-dependent, but the supplied CVSS rates attack complexity as low. No remote attack path is identified.
Researcher notes
The disclosed root cause is registration ordering within the mpu3050 probe lifecycle. The sources do not describe the precise corruptible object, triggering sequence, reliability, or demonstrated impact. Multiple Linux stable commit references appear to represent branch-specific fixes. Avoid inferring affected ranges from the bundle's isolated version strings.
Mitigation direction
Update to a vendor-supported kernel containing the applicable Linux stable fix.
Check Linux distributor or appliance-vendor guidance for exact fixed package versions.
Reduce untrusted local code execution on exposed systems until updates are applied.
Validation and detection
Inventory exact kernel and distributor build versions across potentially affected systems.
Determine whether the MPU3050 IIO driver is built, loaded, or operationally required.
Confirm installed vendor kernels incorporate the applicable referenced stable commit.
Recheck vendor advisories because the bundle's affected-version boundaries are unclear.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2026-31761 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
11Source links
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.