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

  scsi: qla2xxx: Serialize NVMe unsol ctx list with a per-fcport lock

  The fcport->unsol_ctx_head list is modified from several contexts without
  a common lock
summary: |-
  In the Linux kernel, the following vulnerability has been resolved:

  scsi: qla2xxx: Serialize NVMe unsol ctx list with a per-fcport lock

  The fcport->unsol_ctx_head list is modified from several contexts without
  a common lock. Entries ar…
severity: high
cvss: 8.8
cvssVector: 'CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H'
vendor: Linux
product: Linux
affected:
  - >-
    Linux >= 875386b98857822b77ac7f95bdf367b70af5b78c <
    b211d138cad86f749826d6132db6388eded992d8
  - >-
    Linux >= 875386b98857822b77ac7f95bdf367b70af5b78c <
    4d8ad6bc8cc5eff1870cef00a0d611f38f8b6bd0
  - >-
    Linux >= 875386b98857822b77ac7f95bdf367b70af5b78c <
    76da0c43c63eb0496649e372ac64466364d0fe7d
  - Linux 6.6
published: '2026-09-25'
updated: '2026-09-25'
sourceUpdated: '2026-09-25T15:17:58.053'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2026-97527'
references:
  - url: 'https://git.kernel.org/stable/c/4d8ad6bc8cc5eff1870cef00a0d611f38f8b6bd0'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/76da0c43c63eb0496649e372ac64466364d0fe7d'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/b211d138cad86f749826d6132db6388eded992d8'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
tags:
  - nvd
  - cve.org
ingestedAt: '2026-09-25T11:06:38.926Z'
---

## Overview

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

scsi: qla2xxx: Serialize NVMe unsol ctx list with a per-fcport lock

The fcport->unsol_ctx_head list is modified from several contexts without
a common lock. Entries are added in qla2xxx_process_purls_iocb() from the
response queue ISR (under the qpair qp_lock), while they are removed from
qla2xxx_process_purls_pkt() (DPC/purex worker), qla_nvme_xmt_ls_rsp()
(NVMe-FC transport callback) and qla_nvme_release_lsrsp_cmd_kref() (SRB
completion). The qpair qp_lock cannot serialize this per-fcport list since
multiqueue adapters add entries through different qpairs, so a concurrent
add and delete (or two concurrent deletes) can corrupt the list pointers.

Introduce a dedicated per-fcport spinlock, unsol_ctx_lock, initialized in
qla2x00_alloc_fcport(), and take it around every list_add_tail()/list_del()
on unsol_ctx_head. The add nests under the existing qp_lock; no delete path
takes qp_lock, so the lock order is consistent and deadlock free.

## Remediation

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