Local system hang via nested driver registration
Published Apr 27, 2026 · Updated Apr 27, 2026
Improper locking in Linux kernel OMAP GPIO support allows local users to hang the system during vulnerable driver probing. The omap_gpio_probe path calls omap_mpuio_init, which registers omap_mpuio_driver while the driver core already holds a device lock. The condition requires OMAP GPIO support and entry into the affected probe path; the resulting deadlock interrupts system availability.
Summary
What happened
Improper locking in Linux kernel OMAP GPIO support allows local users to hang the system during vulnerable driver probing. The omap_gpio_probe path calls omap_mpuio_init, which registers omap_mpuio_driver while the driver core already holds a device lock. The condition requires OMAP GPIO support and entry into the affected probe path; the resulting deadlock interrupts system availability.
The record
- CVE
- CVE-2026-31687
- Published
- Apr 27, 2026
- Updated
- Apr 27, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-667, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 27, 2026CVE publishedPublication date reported by the CVE source.
- Apr 27, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=11a78b7944963a8b052be46108d07a3ced9e2762 <1c04c3a4de8d4bcb9202f94c44f26c57c2572308
- Affected versionversion=11a78b7944963a8b052be46108d07a3ced9e2762 <2211d77892913804d16c28c7415b82804ab1e54c
- Affected versionversion=11a78b7944963a8b052be46108d07a3ced9e2762 <32f08c3ddd6dda6cbb6c9d715de10f21dccde50f
- Affected versionversion=11a78b7944963a8b052be46108d07a3ced9e2762 <57bcd3feffa79544c73a1a1872472389a391cc79
- Affected versionversion=11a78b7944963a8b052be46108d07a3ced9e2762 <730e5ebff40c852e3ea57b71bf02a4b89c69435f
- Affected versionversion=11a78b7944963a8b052be46108d07a3ced9e2762 <86588916e1887a5edb8a9161cd7ae81e47a7ed25
- Affected versionversion=11a78b7944963a8b052be46108d07a3ced9e2762 <a29215961d833f4de33a09c3964d31ebc6083033
- Affected versionversion=2.6.22
- Affected versionversion=8d76b2488eb3cc0717ab81b60622cff4a5f90f79 <53a76425e0764421ba93bb9045d2e454667d5687
- Affected versionversion=adc1796eced46b48e23ec200a219d635f33a38ee <673dafb9a86349a12a93151fd467625614dc7e12
- Affected versionversion=bc82e5f4d7dc8237ae8cabc73aa46fc93c85d98c <03db4dc9ad6eb91e640b517e00373ce877682854
- Affected versionversion=cd0e0a76e40c2e77bcfc88291d00dca22b00158e <a7fa9460b86f810913b6779461d0448e7c11214c
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo