Skip to main content

Linux Kernel CVE-2025-68218

HIGH
2025-12-16 416baaa9-dc9f-4396-8d5f-8c081fb06d67
High
Disputed · 7.5 Vendor: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Share

Severity by source

Sources disagree (Low–High)
Vendor (416baaa9-dc9f-4396-8d5f-8c081fb06d67) PRIMARY
7.5 HIGH
AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
vuln.today AI
4.7 MEDIUM

Local host-side trigger (AV:L), timing-dependent race (AC:H), needs local privilege to drive NVMe/partition operations (PR:L), availability-only hang (A:H) with no C/I impact.

3.1 AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
4.0 AV:L/AC:H/AT:P/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
SUSE
5.5 MEDIUM
AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
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: 416baaa9-dc9f-4396-8d5f-8c081fb06d67

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

Lifecycle Timeline

2
Analysis Generated
Jul 30, 2026 - 07:21 vuln.today
CVE Published
Dec 16, 2025 - 14:15 cve.org
HIGH 7.5

DescriptionCVE.org

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

nvme-multipath: fix lockdep WARN due to partition scan work

Blktests test cases nvme/014, 057 and 058 fail occasionally due to a lockdep WARN. As reported in the Closes tag URL, the WARN indicates that a deadlock can happen due to the dependency among disk->open_mutex, kblockd workqueue completion and partition_scan_work completion.

To avoid the lockdep WARN and the potential deadlock, cut the dependency by running the partition_scan_work not by kblockd workqueue but by nvme_wq.

AnalysisAI

Denial of service in the Linux kernel's NVMe multipath subsystem allows a lockdep-detected deadlock among disk->open_mutex, the kblockd workqueue, and partition_scan_work completion, which can hang block-device operations. The fix moves partition_scan_work off the kblockd workqueue onto nvme_wq to break the lock-dependency cycle. No public exploit identified at time of analysis; the issue surfaces intermittently during NVMe partition scanning on systems using NVMe multipath.

Technical ContextAI

The affected component is the kernel's nvme-multipath driver, which presents multiple physical paths to an NVMe namespace as a single block device. When a multipath device is scanned for partitions, partition_scan_work was queued on the shared kblockd workqueue. This created a circular lock dependency: block-layer partition scanning takes disk->open_mutex, while completion of work on kblockd and completion of partition_scan_work interlock, so lockdep flags a potential ABBA deadlock. The root cause is a classic lock-ordering / workqueue-dependency violation (CWE-833-class deadlock; CWE field is provided as N/A in the input). The fix isolates partition_scan_work on the dedicated nvme_wq workqueue so its completion no longer depends on kblockd, cutting the cycle.

Affected ProductsAI

The Linux kernel's nvme-multipath driver is affected; the input does not enumerate exact vulnerable version ranges or CPE strings, and the CWE is listed as N/A. Fix commits are published on git.kernel.org stable trees (6d87cd5335784351280f82c47cc8a657271929c3, 89456dab7ba5ab63d60945440926673a3205e829, b03eb63288a8ffe3adfb34e68309c8e2edb06d0b, e2a897ad5f538d314955c747a0a2edb184fcdecd, ef4ab2a8abe554379e10303ae86f7c501336ba0d), indicating backports across multiple stable branches; administrators should map these commit hashes to their distribution kernel to determine exposure. Only systems using NVMe with multipath enabled are practically affected.

RemediationAI

Upstream fix available (multiple stable-tree commits); a released patched tagged version is not independently confirmed from the input - apply your distribution's kernel update that incorporates the nvme-multipath partition_scan_work change (git.kernel.org commits 6d87cd5, 89456da, b03eb63, e2a897a, ef4ab2a). No practical pre-patch workaround targets the flaw directly since it is an internal scheduling/lock-ordering defect; where kernel updates cannot be applied immediately, the exposure is limited to hosts running NVMe multipath, and the failure mode is a lockdep warning / potential hang rather than compromise, so risk-based deferral to the next maintenance window is reasonable. Avoid unnecessary manual partition rescans of NVMe multipath devices as a low-value operational precaution, noting this does not eliminate the underlying race.

Vendor StatusVendor

SUSE

Severity: Moderate
Product Status
Container suse/sl-micro/6.0/baremetal-os-container:latest Container suse/sl-micro/6.0/toolbox:latest Affected
Container suse/sl-micro/6.0/base-os-container:2.1.3-7.95 Image SL-Micro Image SLE-Micro Image SLE-Micro-Azure Image SLE-Micro-BYOS Image SLE-Micro-BYOS-Azure Image SLE-Micro-BYOS-EC2 Image SLE-Micro-BYOS-GCE Image SLE-Micro-EC2 Image SLE-Micro-GCE Affected
Container suse/sl-micro/6.0/kvm-os-container:2.1.3-6.115 Affected
Container suse/sl-micro/6.0/rt-os-container:2.1.3-7.146 Affected
Container suse/sl-micro/6.1/base-os-container:2.2.1-5.80 Image SL-Micro-Azure Image SL-Micro-BYOS-Azure Image SL-Micro-BYOS-EC2 Image SL-Micro-BYOS-GCE Image SL-Micro-EC2 Image SUSE-Multi-Linux-Manager-Proxy-BYOS-Azure Image SUSE-Multi-Linux-Manager-Proxy-BYOS-EC2 Image SUSE-Multi-Linux-Manager-Proxy-BYOS-GCE Image SUSE-Multi-Linux-Manager-Server-Azure-llc Image SUSE-Multi-Linux-Manager-Server-Azure-ltd Image SUSE-Multi-Linux-Manager-Server-BYOS-Azure Image SUSE-Multi-Linux-Manager-Server-BYOS-EC2 Image SUSE-Multi-Linux-Manager-Server-BYOS-GCE Image SUSE-Multi-Linux-Manager-Server-EC2-llc Image SUSE-Multi-Linux-Manager-Server-EC2-ltd Affected

Share

CVE-2025-68218 vulnerability details – vuln.today

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