Linux Kernel up to 6.19.11 iio iio_device_register race condition

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
6.1$0-$5k0.00

Summaryinfo

A vulnerability was found in Linux Kernel up to 6.19.11. It has been classified as critical. Impacted is the function iio_device_register of the component iio. This manipulation causes race condition. This vulnerability appears as CVE-2026-31761. There is no available exploit. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability was found in Linux Kernel up to 6.19.11. It has been declared as critical. Affected by this vulnerability is the function iio_device_register of the component iio. The manipulation with an unknown input leads to a race condition vulnerability. The CWE definition for the vulnerability is CWE-362. The product contains a code sequence that can run concurrently with other code, and the code sequence requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence that is operating concurrently. The impact remains unknown. The summary by CVE is:

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.

The advisory is shared at git.kernel.org. This vulnerability is known as CVE-2026-31761 since 03/09/2026. The exploitation appears to be difficult. Technical details are known, but no exploit is available.

Upgrading to version 5.10.253, 5.15.203, 6.1.168, 6.6.134, 6.12.81, 6.18.22 or 6.19.12 eliminates this vulnerability. Applying the patch 22487ef85f6dd9499ddf49b85a08afc50a3f1992/caec338f91469f0a70b68165185afa3abc994545/051ca43b0e0e4b66bfd349cd53ccf231ad1d69b7/2a4537653d200fda2a8516083459f8ff6194f8fc/92f18aa86302fe83e0726a1191015f427d4ff056/cc3de12a5612ee25df7fb549cb7b3e4cc8bfaf9c/59a317f8215674c8330817770497301bfb2c1b99/4c05799449108fb0e0a6bd30e65fffc71e60db4d is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 6.2
VulDB Meta Temp Score: 6.1

VulDB Base Score: 4.6
VulDB Temp Score: 4.4
VulDB Vector: 🔒
VulDB Reliability: 🔍

CNA Base Score: 7.8
CNA Vector (Linux): 🔒

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Race condition
CWE: CWE-362
CAPEC: 🔒
ATT&CK: 🔒

Physical: Partially
Local: Yes
Remote: Partially

Availability: 🔒
Status: Not defined

EPSS Score: 🔒
EPSS Percentile: 🔒

Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Kernel 5.10.253/5.15.203/6.1.168/6.6.134/6.12.81/6.18.22/6.19.12
Patch: 22487ef85f6dd9499ddf49b85a08afc50a3f1992/caec338f91469f0a70b68165185afa3abc994545/051ca43b0e0e4b66bfd349cd53ccf231ad1d69b7/2a4537653d200fda2a8516083459f8ff6194f8fc/92f18aa86302fe83e0726a1191015f427d4ff056/cc3de12a5612ee25df7fb549cb7b3e4cc8bfaf9c/59a317f8215674c8330817770497301bfb2c1b99/4c05799449108fb0e0a6bd30e65fffc71e60db4d

Timelineinfo

03/09/2026 CVE reserved
05/01/2026 +52 days Advisory disclosed
05/01/2026 +0 days VulDB entry created
07/17/2026 +77 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2026-31761 (🔒)
GCVE (CVE): GCVE-0-2026-31761
GCVE (VulDB): GCVE-100-360673

Entryinfo

Created: 05/01/2026 17:54
Updated: 07/17/2026 10:42
Changes: 05/01/2026 17:54 (59), 07/17/2026 10:42 (11)
Complete: 🔍
Cache ID: 216::103

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

Do you know our Splunk app?

Download it now for free!