Go to homepageCyberStrike

Menu

Star on GitHub · 3.2k
Sign inDownload

CVE-2026-31687

5.5 · MEDIUM

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_dr…

Published Apr 27, 2026CWE-667EPSS 0.13%

Overview

CVE-2026-31687 is a medium-severity vulnerability. It was published on April 27, 2026 and has a CVSS 3.1 base score of 5.5 (MEDIUM).

This vulnerability has a CVSS 3.1 base score of 5.5, rated MEDIUM. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

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

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

References

Refgit.kernel.org/stable/c/03db4dc9ad6eb91e640b517e00373ce877682854Refgit.kernel.org/stable/c/1c04c3a4de8d4bcb9202f94c44f26c57c2572308Refgit.kernel.org/stable/c/2211d77892913804d16c28c7415b82804ab1e54cRefgit.kernel.org/stable/c/32f08c3ddd6dda6cbb6c9d715de10f21dccde50fRefgit.kernel.org/stable/c/53a76425e0764421ba93bb9045d2e454667d5687Refgit.kernel.org/stable/c/57bcd3feffa79544c73a1a1872472389a391cc79Refgit.kernel.org/stable/c/673dafb9a86349a12a93151fd467625614dc7e12Refgit.kernel.org/stable/c/730e5ebff40c852e3ea57b71bf02a4b89c69435fRefgit.kernel.org/stable/c/86588916e1887a5edb8a9161cd7ae81e47a7ed25Refgit.kernel.org/stable/c/a29215961d833f4de33a09c3964d31ebc6083033

How CyberStrike helps

Frequently asked questions

What is CVE-2026-31687?

CVE-2026-31687 is a medium-severity vulnerability. It was published on April 27, 2026 and has a CVSS 3.1 base score of 5.5 (MEDIUM).

How severe is CVE-2026-31687?

This vulnerability has a CVSS 3.1 base score of 5.5, rated MEDIUM. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2026-31687?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2026-31687?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2026-31687 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related MEDIUM CVEs from 2026

View all
Browse by year2026202520242023202220212020201920182017201620152014201320122011201020092008200720062005200420032002200120001999