Skip to main content

Linux Kernel EUVDEUVD-2026-35428

| CVE-2026-46327 HIGH
Race Condition (CWE-362)
2026-06-09 Linux GHSA-w5j4-wm72-f9fp
High
Disputed · 7.8 Vendor: Linux
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Recon
    Obtain local shell with low privileges
  2. Delivery
    Identify dm-managed zoned block device
  3. Exploit
    Issue concurrent report-zones operations
  4. Install
    Race dm suspend state check
  5. C2
    Trigger TOCTOU on live mapping table
  6. Execute
    Corrupt kernel memory or panic
  7. Impact
    Escalate to root or DoS

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V15 - Secure Coding and Architecture Concurrency control, locking
MITRE ATT&CK

1 technique across 1 tactic: Privilege Escalation

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Attacker must have local code execution with low privileges (PR:L) on a Linux host where a zoned block device is exposed through the device-mapper subsystem and accessible to the attacker for issuing report-zones operations. The attacker must also be able to race the dm suspend transition window, which typically requires concurrent administrative activity or a way to influence suspend timing. Limiting factors: AV:L means no network exploitation, the bug only manifests on systems using dm with zoned devices (uncommon outside of SMR/ZNS deployments), and timing-dependent race exploitation is non-trivial in practice - substantially narrowing real-world impact despite the 7.8 CVSS.

Impact

The CVSS 3.1 base score of 7.8 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) reflects a local, low-complexity, low-privilege flaw with high CIA impact - typical scoring for kernel race conditions that could yield memory corruption. However, EPSS is extremely low at 0.02% (5th percentile) and there is no CISA KEV listing and no public exploit identified, indicating no observed real-world exploitation. Practical exploitability requires (a) a zoned block device exposed through device-mapper and (b) the ability to race the suspend path - narrow preconditions that meaningfully limit the attack surface despite the high CVSS. This is a legitimate stability/correctness fix that distributions should ship in routine kernel updates, but it is not an urgent emergency-patch candidate for most environments.

Exploit ScenarioDerived

A local low-privileged user with the ability to issue blk-report-zones ioctls/sysfs reads against a device-mapper-managed zoned block device repeatedly races the dm suspend/resume path (triggered by another permitted operation or by a parallel admin action) to dereference a stale or partially torn-down mapping table. Successful exploitation could yield kernel memory corruption leading to local privilege escalation, information disclosure, or a kernel panic. No public PoC is known at time of analysis.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Jun 14, 2026

Race condition in the Linux kernel device-mapper (dm) subsystem allows a local privileged user to trigger memory corruption or use-after-free conditions by exploiting a TOCTOU flaw in dm_blk_report_zones, which calls dm_suspended_md without holding required locks. The flaw affects multiple stable kernel branches including 6.12.x, 6.15.x, 6.16, and 6.18.x prior to fixed releases. No public exploit identified at time of analysis, and EPSS scores exploitation probability at 0.02% (5th percentile).

RemediationAI

Vendor-released patches are available - upgrade to the fixed stable kernel for your branch: 6.12.75 or later for the 6.12 LTS series, 6.18.14 or later, 6.19.4 or later, or 7.0. The upstream commits are 175ac0a6115400278d3900f5a04a58b17b3f6cd0, 7a3385e97af2b6f485fef11e82d8c29adee4be93, d809a36692ee1394cac85ce6ba7cf8ea58da5812, and 24c405fdbe215c45e57bba672cc42859038491ee, all available under https://git.kernel.org/stable/c/. Distribution users should track their vendor's kernel update for the corresponding backport. As a temporary compensating control where patching is delayed, avoid exposing zoned block devices through device-mapper targets and restrict local shell access to trusted users; note this materially reduces functionality for ZNS/SMR workloads, so it is only acceptable on systems that do not use zoned storage via dm.

Affected VersionsENISA

Linux patch: 0
Linux patch: 6.18.14
Linux 6.16
Linux 37f53a2c60d03743e0eacf7a0c01c279776fef4e <24c405fdbe215c45e57bba672cc42859038491ee
Linux patch: 7.0
Linux 6.15.3 <6.16
Linux patch: 6.12.75
Linux patch: 6.19.4
Linux f9c1bdf24615303d48a2d0fd629c88f3189563aa <175ac0a6115400278d3900f5a04a58b17b3f6cd0
Linux d19bc1b4dd5f322980b1f05f79b2ea4f0db10920
Linux 6.12.34 <6.12.75
Linux 37f53a2c60d03743e0eacf7a0c01c279776fef4e <7a3385e97af2b6f485fef11e82d8c29adee4be93
Linux 37f53a2c60d03743e0eacf7a0c01c279776fef4e <d809a36692ee1394cac85ce6ba7cf8ea58da5812

Affected Packages

euvd linux fix: 6.12.75, 6.16

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The vulnerability resides in the Linux device-mapper (dm) layer, specifically in dm_blk_report_zones - the block-device report-zones handler used for zoned block devices (e.g., SMR HDDs, ZNS SSDs). The function tested dm_suspended_md() without serialization, creating a classic Time-of-Check to Time-of-Use (TOCTOU) race: the suspended state could change between the check and subsequent operations on the live mapping table. The fix re-orders the call so dm_suspended_md is invoked after dm_get_live_table, which ensures the live table reference protects the suspend state from changing concurrently. This is a race-condition class bug (broadly CWE-362 / CWE-367) in kernel block-layer code, although no CWE was formally assigned.

Know when the next one hits your stack

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

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

Local access with low privileges (PR:L) is required; AC:H reflects the timing-dependent race against dm suspend; successful exploitation can yield full kernel memory corruption (C/I/A:H).

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:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
SUSE 4.7 MEDIUM
AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
Red Hat 5.5 LOW

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

4
CVSS changed
Jun 14, 2026 - 06:22 NVD
7.8 (HIGH)
Patch available
Jun 09, 2026 - 15:01 EUVD
CVE Published
Jun 09, 2026 - 12:25 cve.org
HIGH 7.8
CVE Published
Jun 09, 2026 - 12:25 nvd
UNKNOWN (no severity yet)

DescriptionCVE.org

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

dm: fix unlocked test for dm_suspended_md

The function dm_blk_report_zones tests if the device is suspended with the "dm_suspended_md" call. However, this function is called without holding any locks, so the device may be suspended just after it.

Move the call to dm_suspended_md after dm_get_live_table, so that the device can't be suspended after the suspended state was tested.

Executive ViewAI

Why It Matters

A race condition in the Linux kernel device-mapper subsystem (CVE-2026-46327) affects kernel versions 6.12.x through 6.18.x and permits local privileged users to trigger memory corruption or use-after-free conditions in a critical disk management component. No public exploit has been identified, though any organization running vulnerable kernel versions faces operational risk and potential system instability. Immediate kernel updates are required for all affected production systems.

Business Impact: High
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.0%
Top 95% exploitable
Data Quality
6 sources
Confidence: High

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.0%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
None
System Exposure· derived
Small
Automatable· derived
No
Human Impact
High

Priority Score

39
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +39
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

Race conditions occur when multiple concurrent requests exploit the brief time gap between checking a condition and acting upon it (TOCTOU - Time of Check, Time of Use).

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 Performance Computing 15 SP7 Affected

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