Skip to main content

Linux Kernel EUVDEUVD-2026-25884

| CVE-2026-31687 MEDIUM
Improper Locking (CWE-667)
2026-04-27 Linux
Red Hat Suse Information Disclosure Linux
5.5
CVSS 3.1 · NVD
Share

Severity by source

NVD PRIMARY
5.5 MEDIUM
AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
SUSE
MEDIUM
qualitative

Primary rating from NVD.

CVSS VectorNVD

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

Lifecycle Timeline

7
Analysis Generated
May 06, 2026 - 21:31 vuln.today
CVSS changed
May 06, 2026 - 19:07 NVD
5.5 (MEDIUM)
Patch available
Apr 27, 2026 - 19:01 EUVD
Patch released
Apr 27, 2026 - 18:32 nvd
Patch available
EUVD ID Assigned
Apr 27, 2026 - 18:00 euvd
EUVD-2026-25884
CVE Published
Apr 27, 2026 - 17:32 nvd
N/A
CVE Published
Apr 27, 2026 - 17:32 nvd
MEDIUM 5.5

DescriptionCVE.org

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

AnalysisAI

Denial of service in Linux kernel GPIO OMAP driver allows local authenticated users to crash the system via a deadlock condition triggered by improper driver registration from probe() callback. The vulnerability stems from registering the omap_mpuio_driver within omap_gpio_probe(), which violates driver core locking rules and creates a potential deadlock when device_lock enforcement was strengthened in commit dc23806a7c47. EPSS score of 0.03% reflects low exploitation probability despite availability of patched kernel versions.

Technical ContextAI

The Linux kernel GPIO OMAP subsystem (gpio/omap.c) implements GPIO functionality for ARM OMAP processors. Commit 11a78b794496 introduced a flaw where the omap_mpuio_driver is registered from within omap_mpuio_init(), which is called as part of omap_gpio_probe(). The probe() function is a driver callback executed while the device lock is already held. Commit dc23806a7c47 strengthened driver core enforcement to prevent driver_match_device() calls while holding device_lock, exposing the architectural violation. The CWE-667 (Improper Locking) classification identifies the root cause: improper synchronization between the GPIO driver probe sequence and driver core locking requirements. The fix involves moving driver registration from probe time to module initialization via module_init() and adding corresponding module_exit() cleanup, eliminating the lock contention and the unregistration leak.

RemediationAI

Apply the upstream fix by upgrading to a patched kernel version from the affected stable branches: Linux 5.10.251 or later for 5.10.x, 5.15.201 or later for 5.15.x, 6.1.164 or later for 6.1.x, 6.6.125 or later for 6.6.x, 6.12.72 or later for 6.12.x, or 6.18.11 or later for 6.18.x. The fix moves omap_mpuio_driver registration from omap_gpio_probe() to module_init() and adds module_exit() cleanup, eliminating the deadlock condition. Verify that your system uses the OMAP GPIO driver (typically ARM OMAP platforms like BeagleBone, Pandaboard) before prioritizing this patch; non-OMAP systems are unaffected. References for kernel source and patch details are available at https://git.kernel.org/stable/ with commit hashes provided in the CVE references.

Same weakness CWE-667 – Improper Locking

View all
CVE-2025-43510 HIGH POC
7.8
CVE-2019-5886 CRITICAL POC
9.8
CVE-2020-13246 HIGH POC
7.5
CVE-2019-15513 HIGH POC
7.5
CVE-2019-11599 HIGH POC
7.0
CVE-2023-21400 MEDIUM POC
6.7
CVE-2021-20291 MEDIUM POC
6.5
CVE-2020-12658 CRITICAL
9.8

Same technique Information Disclosure

View all
CVE-2013-2251 CRITICAL POC
9.8
CVE-2017-5638 CRITICAL POC
9.8
CVE-2025-24813 CRITICAL POC
9.8
CVE-2015-1701 HIGH POC
7.8
CVE-2017-0147 HIGH POC
7.5
CVE-2014-6324 HIGH POC
8.8
CVE-2023-7028 CRITICAL POC
10.0
CVE-2017-0213 HIGH POC
7.3

Vendor StatusVendor

SUSE

Severity: Medium
Product Status
SUSE Linux Enterprise Desktop 15 SP7 Fixed
SUSE Linux Enterprise Desktop 15 SP7 Fixed
SUSE Linux Enterprise High Availability Extension 15 SP7 Fixed
SUSE Linux Enterprise High Availability Extension 15 SP7 Fixed
SUSE Linux Enterprise High Performance Computing 15 SP7 Fixed

Share

EUVD-2026-25884 vulnerability details – vuln.today
Back

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy