# CVE-2026-31687: gpio: omap: do not register driver in probe()

> A race condition in the Linux kernel GPIO driver can cause a deadlock, leading to a denial of service.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 27 Apr 2026
- **Updated:** 23 May 2026
- **Also known as:** BELL-CVE-2026-31687, DEBIAN-CVE-2026-31687, GHSA-wvmf-v9m3-rvrr, ROOT-OS-UBUNTU-2204-CVE-2026-31687, ROOT-OS-UBUNTU-2404-CVE-2026-31687, UBUNTU-CVE-2026-31687

## What is CVE-2026-31687?

CVE-2026-31687 is a medium-severity vulnerability in Linux kernel, published on 27 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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().

Weakness: CWE-667 (Improper Locking)

## Which versions are affected by CVE-2026-31687?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2026-31687?

Apply the vendor's patch.

## Is CVE-2026-31687 being exploited?

There is no known exploitation of CVE-2026-31687 in the wild and no public exploit code.

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-31687 and fix it if it is affected.

What it is: CVE-2026-31687 is a medium-severity vulnerability in Linux kernel, published on 27 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-31687 in the wild and no public exploit code.

Affected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-31687/ (Markdown: https://insights.sbomify.com/CVE-2026-31687/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-31687
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-31687
- OSV: https://osv.dev/vulnerability/CVE-2026-31687

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-31687/
Summaries are generated and may contain mistakes; the official description above is the record.