---
id: CVE-2025-68218
title: |-
  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
summary: |-
  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 Close…
severity: high
cvss: 7.5
cvssVector: 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H'
published: '2025-12-16'
updated: '2026-10-14'
sourceUpdated: '2026-10-14T13:10:00.187'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2025-68218'
references:
  - url: 'https://git.kernel.org/stable/c/6d87cd5335784351280f82c47cc8a657271929c3'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/89456dab7ba5ab63d60945440926673a3205e829'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/b03eb63288a8ffe3adfb34e68309c8e2edb06d0b'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/e2a897ad5f538d314955c747a0a2edb184fcdecd'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/ef4ab2a8abe554379e10303ae86f7c501336ba0d'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
tags:
  - nvd
epss: 0.00528
epssPercentile: 0.43122
ingestedAt: '2026-10-14T13:30:58.457Z'
---

## Overview

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.

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.
