LiveActive security incident?Get immediate response
CVE Record

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.

HighCVSS 7.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

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.
Prepared
Confidence
medium
Sources
10

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.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9Linux

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2026-31761Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

siemens-SADPADP container
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux3904b28efb2c780c23dcddfb87e07fe0230661e5, 3904b28efb2c780c23dcddfb87e07fe0230661e5, 3904b28efb2c780c23dcddfb87e07fe0230661e5, 3904b28efb2c780c23dcddfb87e07fe0230661e5, 3904b28efb2c780c23dcddfb87e07fe0230661e5, 3904b28efb2c780c23dcddfb87e07fe0230661e5, 3904b28efb2c780c23dcddfb87e07fe0230661e5, 3904b28efb2c780c23dcddfb87e07fe0230661e5unaffected
LinuxLinux4.10, 0, 5.10.253, 5.15.203, 6.1.168, 6.6.134, 6.12.81, 6.18.22, 6.19.12, 7.0affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.