CVE-2026-31687

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

Package Linux Kernel
Published 2026-04-27
Last modified 2026-05-06
CVSS version 3.1
Patch available
Yes

CVSS 3.1 score

5.5

out of 10
Medium
Attack Vector
Local
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
High
Vector string
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Weakness type

CWE-667

CVE-2026-31687 is a Improper Locking vulnerability

What is Improper Locking?

The product does not properly acquire or release a lock, which can lead to unexpected behaviour. Learn more on MITRE CWE

Affected versions

Linux kernel versions 6.6.125, 6.12.72, 6.18.11, 6.19.1, 2.6.22 and later are affected. Fixed in 5.10.251, 5.15.201, 6.1.164, 6.6.125, 6.6.126, 6.12.72, 6.12.73, 6.18.11, 6.18.12, 6.19.2, 6.19 and their respective stable series.

Affected from
≥ 6.6.125 ≥ 6.12.72 ≥ 6.18.11 ≥ 6.19.1 ≥ 2.6.22
Fixed in
✓ 5.10.251 5.10.x ✓ 5.15.201 5.15.x ✓ 6.1.164 6.1.x ✓ 6.6.125 6.6.x ✓ 6.6.126 6.6.x ✓ 6.12.72 6.12.x ✓ 6.12.73 6.12.x ✓ 6.18.11 6.18.x ✓ 6.18.12 6.18.x ✓ 6.19.2 6.19.x ✓ 6.19

References

The following references provide additional information about CVE-2026-31687 including vendor advisories, patch commits, exploit details, and third-party analysis. Links are sourced from the NIST NVD database.

11 patch commits total View all on NVD

Frequently asked questions

  • What is CVE-2026-31687?

    CVE-2026-31687 is a Medium severity Linux kernel vulnerability with a CVSS score of 5.5 out of 10 , classified as an Improper Locking flaw (CWE-667) . It affects Linux kernel versions from 6.6.125 onward and has been patched in 5.10.251, 5.15.201, 6.1.164 and others. CVE-2026-31687 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.

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

    CVE-2026-31687 has a CVSS score of 5.5 out of 10, rated Medium severity (CVSS 3.1). The vector string is CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H .

  • Is there a patch available for CVE-2026-31687?

    Yes — CVE-2026-31687 has been patched. Fixed versions include 5.10.251, 5.15.201, 6.1.164 and others. If you are running Linux kernel 6.6.125 or later up to the fix versions, apply the relevant patch for your kernel branch.

  • Is CVE-2026-31687 actively exploited?

    No — CVE-2026-31687 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.

  • What is Improper Locking (CWE-667)?

    The product does not properly acquire or release a lock, which can lead to unexpected behaviour. View CWE-667 on MITRE CWE →

Back to
All CVEs
View on
NVD / NIST