VYPR
Unrated severityNVD Advisory· Published Dec 16, 2025· Updated Apr 15, 2026

CVE-2025-68218

CVE-2025-68218

Description

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.

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

A lockdep WARN and potential deadlock in nvme-multipath due to partition scan work running on kblockd is fixed by moving it to nvme_wq.

Vulnerability

Overview

In the Linux kernel's nvme-multipath subsystem, a lockdep WARNING (WARN) was observed during blktests nvme/014, 057, and 058. The warning indicated a potential deadlock involving disk->open_mutex, kblockd workqueue completion, and partition_scan_work completion. The root cause is a circular dependency when partition scanning is scheduled on the kblockd workqueue, which can lead to a deadlock scenario under certain I/O patterns.

Exploitation

Context

This vulnerability is triggered during normal operation of NVMe multipath devices when partition scanning is initiated. No special privileges or network access are required; it can occur in any system using NVMe multipath with kernel versions that include the flawed code. The lockdep warning itself is a diagnostic tool, but the underlying deadlock could cause system hangs or unresponsive storage paths.

Impact

If the deadlock occurs, it can result in a denial of service (DoS) condition where the system becomes unresponsive or storage I/O stalls indefinitely. The lockdep WARN is a symptom of this potential deadlock, which could be exploited by an attacker with local access to trigger the specific I/O patterns that lead to the circular dependency.

Mitigation

The fix, committed in kernel stable trees [1][2], removes the dependency by running partition_scan_work on the nvme_wq workqueue instead of kblockd. This breaks the circular lock dependency and eliminates the lockdep WARN. Users should apply the corresponding kernel update to their distribution. No workaround is available other than updating the kernel.

AI Insight generated on May 19, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.

Affected products

1

Patches

0

No patches discovered yet.

Vulnerability mechanics

AI mechanics synthesis has not run for this CVE yet.

References

5

News mentions

0

No linked articles in our index yet.