Linux Kernel up to 6.19.1 gpio probe deadlock

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.
4.6$0-$5k0.00

Summaryinfo

A vulnerability has been found in Linux Kernel up to 6.19.1 and classified as critical. Impacted is the function probe of the component gpio. Performing a manipulation results in deadlock. This vulnerability is cataloged as CVE-2026-31687. There is no exploit available. The affected component should be upgraded.

Detailsinfo

A vulnerability, which was classified as critical, was found in Linux Kernel up to 6.19.1. This affects the function probe of the component gpio. The manipulation with an unknown input leads to a deadlock vulnerability. CWE is classifying the issue as CWE-833. The product contains multiple threads or executable segments that are waiting for each other to release a necessary lock, resulting in deadlock. This is going to have an impact on availability. The summary by CVE is:

In the Linux kernel, the following vulnerability has been resolved: gpio: omap: do not register driver in probe() Commit 11a78b794496 ("ARM: OMAP: MPUIO wake updates") registers the omap_mpuio_driver from omap_mpuio_init(), which is called from omap_gpio_probe(). However, it neither makes sense to register drivers from probe() callbacks of other drivers, nor does the driver core allow registering drivers with a device lock already being held. The latter was revealed by commit dc23806a7c47 ("driver core: enforce device_lock for driver_match_device()") leading to a potential deadlock condition described in [1]. Additionally, the omap_mpuio_driver is never unregistered from the driver core, even if the module is unloaded. Hence, register the omap_mpuio_driver from the module initcall and unregister it in module_exit().

It is possible to read the advisory at git.kernel.org. This vulnerability is uniquely identified as CVE-2026-31687 since 03/09/2026. The exploitability is told to be difficult. Technical details of the vulnerability are known, but there is no available exploit.

The vulnerability scanner Nessus provides a plugin with the ID 311010 (Linux Distros Unpatched Vulnerability : CVE-2026-31687), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 5.10.251, 5.15.201, 6.1.164, 6.6.125, 6.6.126, 6.12.72, 6.12.73, 6.18.11, 6.18.12 or 6.19.2 eliminates this vulnerability. Applying the patch 57bcd3feffa79544c73a1a1872472389a391cc79/86588916e1887a5edb8a9161cd7ae81e47a7ed25/a29215961d833f4de33a09c3964d31ebc6083033/1c04c3a4de8d4bcb9202f94c44f26c57c2572308/673dafb9a86349a12a93151fd467625614dc7e12/2211d77892913804d16c28c7415b82804ab1e54c/a7fa9460b86f810913b6779461d0448e7c11214c/32f08c3ddd6dda6cbb6c9d715de10f21dccde50f/53a76425e0764421ba93bb9045d2e454667d5687/730e5ebff40c852e3ea57b71bf02a4b89c69435f/03db4dc9ad6eb91e640b517e00373ce877682854 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.

The vulnerability is also documented in the vulnerability database at Tenable (311010). Statistical analysis made it clear that VulDB provides the best quality for 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: 4.8
VulDB Meta Temp Score: 4.6

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

CVSSv2info

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

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

Exploitinginfo

Class: Deadlock
CWE: CWE-833 / CWE-404
CAPEC: 🔒
ATT&CK: 🔒

Physical: No
Local: No
Remote: Partially

Availability: 🔒
Status: Not defined

EPSS Score: 🔒
EPSS Percentile: 🔒

Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 311010
Nessus Name: Linux Distros Unpatched Vulnerability : CVE-2026-31687

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Kernel 5.10.251/5.15.201/6.1.164/6.6.125/6.6.126/6.12.72/6.12.73/6.18.11/6.18.12/6.19.2
Patch: 57bcd3feffa79544c73a1a1872472389a391cc79/86588916e1887a5edb8a9161cd7ae81e47a7ed25/a29215961d833f4de33a09c3964d31ebc6083033/1c04c3a4de8d4bcb9202f94c44f26c57c2572308/673dafb9a86349a12a93151fd467625614dc7e12/2211d77892913804d16c28c7415b82804ab1e54c/a7fa9460b86f810913b6779461d0448e7c11214c/32f08c3ddd6dda6cbb6c9d715de10f21dccde50f/53a76425e0764421ba93bb9045d2e454667d5687/730e5ebff40c852e3ea57b71bf02a4b89c69435f/03db4dc9ad6eb91e640b517e00373ce877682854

Timelineinfo

03/09/2026 CVE reserved
04/27/2026 +48 days Advisory disclosed
04/27/2026 +0 days VulDB entry created
04/30/2026 +3 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2026-31687 (🔒)
GCVE (CVE): GCVE-0-2026-31687
GCVE (VulDB): GCVE-100-359859

Entryinfo

Created: 04/27/2026 20:22
Updated: 04/30/2026 09:41
Changes: 04/27/2026 20:22 (59), 04/30/2026 09:41 (2)
Complete: 🔍
Cache ID: 216::103

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you want to use VulDB in your project?

Use the official API to access entries easily!