What is the CVSS score of EUVD-2026-59213?

EUVD-2026-59213 has a contested CVSS base score of 7.8 from a third party (e.g. CISA-ADP), while the vendor rates it High. vuln.today uses the vendor rating as authoritative.

Which versions of Linux Kernel are affected by EUVD-2026-59213?

A deadlock-handling defect in the Linux kernel regulator subsystem (CVE-2026-72314) threatens availability and privilege escalation on MIPS-based systems, potentially causing kernel panics or local…. A patch is available.

How to fix or mitigate EUVD-2026-59213?

Within 24 hours, audit infrastructure inventory to identify any systems running Linux on MIPS architecture-typically embedded systems, networking equipment, and specialized appliances. Within 7 days, apply the available vendor patch to all identified MIPS systems following your Linux distribution's kernel update procedures. Over the subsequent 30 days, validate post-patch kernel stability, monitor system logs for regulator-related errors, and confirm that power management and voltage regulation subsystems function correctly on patched MIPS deployments.

Linux Kernel EUVD-2026-59213

| CVE-2026-72314 HIGH

2026-08-15 Linux

GHSA-g74q-qxv8-58hq

Information Disclosure Linux Red Hat Canonical Suse

High

Disputed · 7.8 Vendor: Linux

Severity by source

Sources disagree (Low–High)

Vendor (Linux) PRIMARY

7.8 HIGH

AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

vuln.today AI

7.0 HIGH

Race-condition timing on MIPS-only path makes AC:H; PR:L required for local trigger; full kernel impact justified by corrupted locking state.

3.1 AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

4.0 AV:L/AC:H/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

SUSE

2.5 MEDIUM

AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:L

Red Hat

5.5 LOW

qualitative

vuln.today treats the vendor’s rating as authoritative. A higher third-party CVSS (e.g. CISA-ADP) is shown for transparency but does not drive the headline severity.

CVSS VectorVendor: Linux

Attack Vector

Local

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

Analysis Generated

Aug 17, 2026 - 08:22 vuln.today

CVSS changed

Aug 17, 2026 - 06:22 NVD

7.8 (HIGH)

Patch available

Aug 15, 2026 - 07:20 EUVD

CVE Published

Aug 15, 2026 - 05:55 cve.org

HIGH 7.8

CVE Published

Aug 15, 2026 - 05:55 cve.org

UNKNOWN (no severity yet)

DescriptionCVE.org

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

regulator: core: regulator_lock_two() should test for EDEADLK not EDEADLOCK

Compare against -EDEADLK, which is what ww_mutex_lock() actually returns and what every other deadlock check in this file already uses.

Function regulator_lock_two() acquires two regulators via regulator_lock_nested() -> ww_mutex_lock(). On contention, ww_mutex_lock() returns -EDEADLK, which is the caller's signal to drop the lock it holds and retry the acquisition in the canonical order.

However, regulator_lock_two() tests the return value against -EDEADLOCK rather than -EDEADLK. On most architectures, EDEADLK and EDEADLOCK are the same value, so the comparison happens to be correct and the bug is invisible. But on MIPS, SPARC, and PowerPC, those two errors have different values. The test is wrong: a genuine -EDEADLK backoff no longer matches -EDEADLOCK, so instead of unlocking and retrying, the code falls into WARN_ON(ret) and returns with only one of the two regulators locked.

In practice, this is a bug only on MIPS, because the regulator core is not built or used on the other two platforms.

In general, EDEADLK is preferred over EDEADLOCK for new code.

AnalysisAI

The regulator subsystem in the Linux kernel contains a deadlock-handling defect where regulator_lock_two() compares the return value of ww_mutex_lock() against -EDEADLOCK instead of the correct -EDEADLK constant. On MIPS architecture - the only platform where the regulator core is active and these two error constants carry different numeric values - the mismatch causes the kernel to skip the mandatory unlock-and-retry backoff sequence, fire WARN_ON, and return to the caller with only one of the two regulators locked, producing corrupted locking state. No public exploit has been identified and EPSS is very low (0.22%, 13th percentile), but the high CVSS impact ratings (C:H/I:H/A:H) reflect the potential for kernel panic or local privilege escalation on affected MIPS systems.

Technical ContextAI

The Linux kernel regulator core (drivers/regulator/core.c) uses wound-wait (ww) mutexes to safely acquire pairs of regulator objects in a deadlock-free sequence. The ww_mutex_lock() function returns -EDEADLK as the canonical signal for the caller to drop its held lock and retry acquisition in canonical order. The bug is a one-line logic error: regulator_lock_two() compares the return value against -EDEADLOCK, a POSIX alias for the same concept. On x86, ARM, and most architectures both macros expand to the same integer (35), rendering the comparison numerically correct and the bug latent. On MIPS however, EDEADLK=45 and EDEADLOCK=58 differ, causing the backoff check to fail silently and the error handling to fall through into WARN_ON(ret). The regulator core is not compiled or used on SPARC or PowerPC, making MIPS the sole platform where the functional impact materializes. No CWE is formally assigned; the root cause class is an incorrect constant reference in concurrent locking code. Affected CPE: cpe:2.3:a:linux:linux:* across multiple stable branches from 5.4.x through 6.x and 7.x development.

RemediationAI

The primary fix is upgrading to a patched Linux kernel stable release: 5.10.261, 5.15.212, 6.1.178, 6.6.145, 6.12.97, 6.18.40, or development branch 7.1.5 and later. Specific upstream patch commits are available at git.kernel.org/stable (dc804f390fddd9c389edf0976356942e16878d8f, 8e39aa63798ea0a797fd9341419f12ef91df3238, 0c305eac40470a224671858a215963b070f9b2a9, 29a7953e9adea6c7f9e64947745b79158e7cea7f, e2063307ea3b6da74585129ba7b588e8243e2ef0, 346e2d666a29ae7233c56b356a0487eb1d42589b, 153d1b8b5bc30847eb70ad535f62f289aa9217e6, d38f8bd771c4999b797d7074b348cf201414bd34). For MIPS-based systems that cannot be immediately patched, restrict local shell access to limit the privilege surface, and monitor kernel logs for WARN_ON messages in the regulator subsystem as an indicator that the broken path is being hit. Disabling the regulator subsystem via build configuration is not a practical workaround on devices that depend on it for power management; the patch is the only clean fix. Downstream distribution advisories (Red Hat, Ubuntu, SUSE) were not present in the available reference data at time of analysis.

More in Canonical

View all

CVE-2011-3544 CRITICAL Act Now POC

9.8 Oct 19

Oracle Java SE JDK/JRE 7 and 6 Update 27 and earlier allows remote code execution with complete system compromise throug

CVE-2019-11043 CRITICAL Emergency POC

9.8 Oct 28

In PHP versions 7.1.x below 7.1.33, 7.2.x below 7.2.24 and 7.3.x below 7.3.11 in certain configurations of FPM setup it

CVE-2014-6271 CRITICAL Act Now POC

9.8 Sep 24

GNU Bash through 4.3 processes trailing strings after function definitions in the values of environment variables, which

CVE-2013-0422 CRITICAL Emergency POC

9.8 Jan 10

Multiple vulnerabilities in Oracle Java 7 before Update 11 allow remote attackers to execute arbitrary code by (1) using

CVE-2016-3714 HIGH Act Now POC

8.4 May 05

The (1) EPHEMERAL, (2) HTTPS, (3) MVG, (4) MSL, (5) TEXT, (6) SHOW, (7) WIN, and (8) PLT coders in ImageMagick before 6.

CVE-2017-12617 HIGH Act Now POC

8.1 Oct 04

When running Apache Tomcat versions 9.0.0.M1 to 9.0.0, 8.5.0 to 8.5.22, 8.0.0.RC1 to 8.0.46 and 7.0.0 to 7.0.81 with HTT

CVE-2016-8735 CRITICAL Act Now POC

9.8 Apr 06

Remote code execution is possible with Apache Tomcat before 6.0.48, 7.x before 7.0.73, 8.x before 8.0.39, 8.5.x before 8

CVE-2014-7169 CRITICAL Act Now POC

9.8 Sep 25

GNU Bash through 4.3 bash43-025 processes trailing strings after certain malformed function definitions in the values of

CVE-2014-0160 HIGH Act Now POC

7.5 Apr 07

The (1) TLS and (2) DTLS implementations in OpenSSL 1.0.1 before 1.0.1g do not properly handle Heartbeat Extension packe

CVE-2016-5195 HIGH Act Now POC

7.0 Nov 10

Race condition in mm/gup.c in the Linux kernel 2.x through 4.x before 4.8.3 allows local users to gain privileges by lev

CVE-2013-2423 LOW Act Now POC

3.7 Apr 17

Unspecified vulnerability in the Java Runtime Environment (JRE) component in Oracle Java SE 7 Update 17 and earlier, and

CVE-2023-4911 HIGH Act Now POC

7.8 Oct 03

Local privilege escalation in the GNU C Library (glibc) dynamic loader ld.so allows unprivileged local users on affected

Same technique Information Disclosure

View all

CVE-2019-2725 CRITICAL POC

9.8

CVE-2021-34523 CRITICAL POC

9.0

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

Vendor StatusVendor

SUSE

Severity: Moderate

Product	Status
SUSE Linux Enterprise Desktop 15 SP7	Affected
SUSE Linux Enterprise Desktop 15 SP7	Affected
SUSE Linux Enterprise High Availability Extension 15 SP7	Affected
SUSE Linux Enterprise High Availability Extension 15 SP7	Affected
SUSE Linux Enterprise High Availability Extension 16.0	Not-Affected

EUVD-2026-59213 vulnerability details – vuln.today

Back

Linux Kernel EUVD-2026-59213

Severity by source

CVSS VectorVendor: Linux

Lifecycle Timeline

DescriptionCVE.org

AnalysisAI

Technical ContextAI

RemediationAI

More in Canonical

Same technique Information Disclosure

Vendor StatusVendor

SUSE

Share

External POC / Exploit Code