Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-05-01. a secondary CVSS source baseline 7.8; sources differ by 0.0.
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
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.
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
May 1, 2026
July 14, 2026
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| linux | Kernel @ 5.10.253 | — | osv |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
Showing the most recent 100 of 130 total refreshes for this CVE.
linux:Kernel
CWE-362
Explore the affected products and dependency analysis for CVE-2026-31761
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.