How to Fix CVE-2026-31687: gpio: omap: do not register driver in Linux

By Sai Kiran Pandrala

Related fixes

Other vulnerabilities in the same area that are worth patching alongside this one:

• How to Fix CVE-2026-43068: Security Vulnerability in Linux — Security Vulnerability in Linux
• How to Fix CVE-2026-31399: Linux (Bundle Sibling) — Linux (Bundle Sibling)
• How to Fix CVE-2026-43249: Security Vulnerability in Linux , Security Vulnerability in Linux
• How to Fix CVE-2026-43386: Out-of-Bounds Read in Linux , Out-of-Bounds Read in Linux
• How to Fix CVE-2026-43133: Security Vulnerability in Linux , Security Vulnerability in Linux

Last verified: 2026-05-25

CVE-2026-31687 is a gpio: omap: do not register driver in Linux Linux. Fix it by upgrading to 5.10.251, 5.15.201, 6.1.164, 6.6.125, 6.6.126, 6.12.72.

What is CVE-2026-31687?

CVE-2026-31687 is a gpio: omap: do not register driver flaw in Linux Linux. The vendor has not published a verified CVSS metric at the time of writing. It is not currently listed in the CISA Known Exploited Vulnerabilities catalog.

From the source record: 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().

Why it matters in practice: The blast radius depends on how the affected service is exposed. An internet-facing instance with no compensating controls is the highest-risk configuration.

Am I affected?

You are affected if your installation of Linux matches a version listed in the Affected row above.

# Debian/Ubuntu
dpkg -s linux | grep Version
# RHEL/Rocky
rpm -q linux

How to fix CVE-2026-31687

Apply the vendor patch. Target the build named in the Fixed in row above (5.10.251, 5.15.201, 6.1.164, 6.6.125, 6.6.126, 6.12.72). The runnable command set below covers the most common deployment patterns for Linux.

Ubuntu / Debian

sudo apt-get update
sudo apt-get install --only-upgrade linux
dpkg -s linux | grep Version

RHEL / CentOS / Rocky

sudo dnf upgrade linux -y
rpm -q linux

After applying the patch

1. Restart the service or device so the patched binary loads.
2. Confirm the running version matches the Fixed in row using the verification command below.
3. Rotate credentials and API keys that the affected service could access if the asset was exposed during the disclosure window.

If you can't patch immediately

Until the patch lands, narrow the attack surface with these runnable controls.

Restrict network exposure

Block public access to the affected service at the perimeter. Allow only trusted source IPs.

# Linux iptables: only allow trusted admin subnet
sudo iptables -A INPUT -p tcp --dport 443 -s 10.10.10.0/24 -j ACCEPT
sudo iptables -A INPUT -p tcp --dport 443 -j DROP
sudo iptables-save | sudo tee /etc/iptables/rules.v4

# Windows firewall: only allow trusted admin subnet on management port
New-NetFirewallRule -DisplayName "Restrict-Mgmt-Allow" -Direction Inbound -Action Allow `
  -RemoteAddress 10.10.10.0/24 -Protocol TCP -LocalPort 443
New-NetFirewallRule -DisplayName "Restrict-Mgmt-Deny"  -Direction Inbound -Action Block `
  -Protocol TCP -LocalPort 443

Mitigations are temporary. Apply the vendor patch as soon as a maintenance window opens.

How to verify the fix worked

Confirm the patched build is the one actually running.

# Debian/Ubuntu
dpkg -s linux | grep Version
# RHEL/Rocky
rpm -q linux

Expected: a version at or above 5.10.251, 5.15.201, 6.1.164, 6.6.125, 6.6.126, 6.12.72.

Also worth doing: pull recent log windows for indicators of compromise listed in the vendor advisory, and re-run an authenticated vulnerability scan with up-to-date signatures.

Frequently asked questions

Is CVE-2026-31687 being exploited in the wild?

As of 2026-05-25, CVE-2026-31687 is not listed in the CISA Known Exploited Vulnerabilities catalog. Watch the catalog and patch on a normal cadence; KEV status can change as exploitation evidence emerges.

What is the CVSS score for CVE-2026-31687?

A verified CVSS score is not listed in the public record for CVE-2026-31687. Check the vendor advisory and the NVD page for an updated metric.

What version fixes this?

Upgrade to 5.10.251, 5.15.201, 6.1.164, 6.6.125, 6.6.126, 6.12.72.

Will a WAF or IDS rule alone close this?

No. Network filters cut down opportunistic scans but they do not remove the flaw. The vendor patch is the only durable fix.

References

• Official vendor advisory: https://git.kernel.org/stable/c/57bcd3feffa79544c73a1a1872472389a391cc79
• NVD entry: https://nvd.nist.gov/vuln/detail/CVE-2026-31687
• CISA KEV catalog: https://www.cisa.gov/known-exploited-vulnerabilities-catalog
• Additional reference: https://git.kernel.org/stable/c/86588916e1887a5edb8a9161cd7ae81e47a7ed25
• Additional reference: https://git.kernel.org/stable/c/a29215961d833f4de33a09c3964d31ebc6083033
• Additional reference: https://git.kernel.org/stable/c/1c04c3a4de8d4bcb9202f94c44f26c57c2572308
• Additional reference: https://git.kernel.org/stable/c/673dafb9a86349a12a93151fd467625614dc7e12

*Assembled from the official vendor advisory, the NVD record, and the CISA KEV listing on 2026-05-25. Always confirm against the vendor advisory before applying changes in production.*