CVE-2026-31687
Last modified
CVE-2026-31687 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. 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().. EPSS estimates a 0.10% chance of exploitation in the next 30 days.
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().
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 2.6.22, < 5.10.251 | — |
| Linux | Linux Kernel | >= 5.11, < 5.15.201 | — |
| Linux | Linux Kernel | >= 5.16, < 6.1.164 | — |
| Linux | Linux Kernel | >= 6.2, < 6.6.125 | — |
| Linux | Linux Kernel | >= 6.7, < 6.12.72 | — |
| Linux | Linux Kernel | >= 6.13, < 6.18.11 | — |
| Linux | Linux Kernel | 6.19 | Rc1 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-31687?
How severe is CVE-2026-31687?
How do I fix CVE-2026-31687?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-31681In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-31682In the Linux kernel, the following vulnerability has been re…9.1
- CVE-2026-31683In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-31684In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-31685In the Linux kernel, the following vulnerability has been re…9.4
- CVE-2026-31686In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-31688Rejected reason: This CVE ID has been rejected or withdrawn …
- CVE-2026-31689In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-3169A security vulnerability has been detected in Tenda F453 1.0…8.8
- CVE-2026-31690In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-31691In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-31692In the Linux kernel, the following vulnerability has been re…5.5
Are you affected by CVE-2026-31687?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
