Skip to main content

Linux CVE-2026-23420

| EUVDEUVD-2026-18637 MEDIUM
Improper Locking (CWE-667)
2026-04-03 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
Red Hat
5.5 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

5
CVSS changed
Apr 24, 2026 - 15:22 NVD
5.5 (MEDIUM)
Patch available
Apr 16, 2026 - 05:29 EUVD
1a1c28a08d74716f3f8e3a21c86b30d0ff13521a,72c6df8f284b3a49812ce2ac136727ace70acc7c,5feeea59ed142e15c3284d0b1a364c6786bf3487
EUVD ID Assigned
Apr 03, 2026 - 13:45 euvd
EUVD-2026-18637
Analysis Generated
Apr 03, 2026 - 13:45 vuln.today
CVE Published
Apr 03, 2026 - 13:24 nvd
N/A

DescriptionCVE.org

In the Linux kernel, the following vulnerability has been resolved:

wifi: wlcore: Fix a locking bug

Make sure that wl->mutex is locked before it is unlocked. This has been detected by the Clang thread-safety analyzer.

AnalysisAI

Mutex lock-unlock mismatch in the Linux kernel's wlcore Wi-Fi driver allows potential information disclosure or system instability through improper synchronization. The vulnerability occurs when wl->mutex is unlocked without being locked first, detected by the Clang thread-safety analyzer. This affects all Linux kernel versions with the wlcore Wi-Fi driver. No active exploitation has been identified, but the bug creates a race condition that could be leveraged to access shared kernel state.

Technical ContextAI

The wlcore driver is a Wi-Fi chipset driver in the Linux kernel responsible for managing TI Wilink wireless devices. The vulnerability is rooted in improper mutex (mutual exclusion lock) usage-a critical synchronization primitive in kernel code. The bug occurs in the wlcore module where unlock operations are performed without corresponding lock acquisition, violating the mutual exclusion contract. This is a CWE-667 (Improper Locking) issue where the driver fails to properly acquire locks before releasing them, potentially creating race conditions where multiple code paths access shared data structures concurrently. The Clang thread-safety analyzer identified this anti-pattern, which is particularly dangerous in kernel code where concurrent access to driver state is common.

RemediationAI

Vendor-released patches are available across Linux stable kernels. Users should upgrade to patched versions of their respective stable branches: Linux 5.10.y, 5.15.y, 6.1.y, or 6.6.y with the respective commits applied. The upstream fixes can be verified at git.kernel.org/stable/ using the provided commit hashes. Distributions tracking the Linux stable kernel will receive these fixes as part of regular kernel updates. Users unable to immediately patch should avoid loading or using the wlcore Wi-Fi driver if alternative wireless drivers are available, though this impacts wireless connectivity. The most reliable remediation is to update the Linux kernel to a version with the mutex synchronization bug fixed via the stable branch commits referenced.

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

CVE-2026-23420 vulnerability details – vuln.today

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