---
id: CVE-2026-98056
title: |-
  In the Linux kernel, the following vulnerability has been resolved:

  nvme: remove stale namespaces by NSID range during scan

  nvme_scan_ns_list() drops the stale namespaces in each gap in the
  reported NSID list one NSID at a time
summary: |-
  In the Linux kernel, the following vulnerability has been resolved:

  nvme: remove stale namespaces by NSID range during scan

  nvme_scan_ns_list() drops the stale namespaces in each gap in the
  reported NSID list one NSID at a time. Every …
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'
vendor: Linux
product: Linux
affected:
  - >-
    Linux >= 540c801c65eb58e05e0ca38b6fd644a83d7e2b33 <
    c84ad7407fb16b92d9b7a649cc304a9cf3757897
  - >-
    Linux >= 540c801c65eb58e05e0ca38b6fd644a83d7e2b33 <
    f56b2bb4b18b017b056c4c17c66b2c4c54bf6ee4
  - >-
    Linux >= 540c801c65eb58e05e0ca38b6fd644a83d7e2b33 <
    52200fc41a79da430ccf7c126ed837535b087ea2
  - >-
    Linux >= 540c801c65eb58e05e0ca38b6fd644a83d7e2b33 <
    4ed7f3d7d435bf5b63da2814dc9270f5ba896011
  - Linux 4.5
published: '2026-09-25'
updated: '2026-09-25'
sourceUpdated: '2026-09-25T15:18:05.140'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2026-98056'
references:
  - url: 'https://git.kernel.org/stable/c/4ed7f3d7d435bf5b63da2814dc9270f5ba896011'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/52200fc41a79da430ccf7c126ed837535b087ea2'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/c84ad7407fb16b92d9b7a649cc304a9cf3757897'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/f56b2bb4b18b017b056c4c17c66b2c4c54bf6ee4'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
tags:
  - nvd
  - cve.org
ingestedAt: '2026-09-25T11:06:38.844Z'
---

## Overview

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

nvme: remove stale namespaces by NSID range during scan

nvme_scan_ns_list() drops the stale namespaces in each gap in the
reported NSID list one NSID at a time. Every iteration calls
nvme_find_get_ns() to look the namespace up and removes it if it is
present. The loop runs once per NSID in the gap rather than once per
namespace actually present.

NSIDs are 32-bit, so a target with a sparse NSID space can make a
single gap spin the loop billions of times with nothing to remove.

  watchdog: BUG: soft lockup - CPU#4 stuck for 26s!
  Workqueue: nvme-wq nvme_scan_work [nvme_core]
  RIP: 0010:__srcu_read_unlock+0xb/0x20
  Call Trace:
   nvme_find_get_ns+0x7d/0xb0 [nvme_core]
   nvme_scan_ns_list+0xe8/0x280 [nvme_core]
   nvme_scan_work+0x18a/0x280 [nvme_core]
   process_one_work+0x197/0x380
   worker_thread+0x2fe/0x410
   kthread+0xe0/0x100

Rename nvme_remove_invalid_namespaces() to nvme_remove_nsid_range()
and give it an open (start, end) NSID range. ctrl->namespaces is
sorted by NSID, so the whole gap is dropped in a single walk that
stops once end is reached. This bounds the work by the namespaces
that are present instead of by the size of the gap.

## Remediation

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