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

  scsi: qla2xxx: Fix soft lockup polling continuation IOCB signature

  qla27xx_copy_multiple_pkt() and qla27xx_copy_fpin_pkt() poll
  rsp_q->ring_ptr->signature for RESPONSE…
summary: |-
  In the Linux kernel, the following vulnerability has been resolved:

  scsi: qla2xxx: Fix soft lockup polling continuation IOCB signature

  qla27xx_copy_multiple_pkt() and qla27xx_copy_fpin_pkt() poll
  rsp_q->ring_ptr->signature for RESPONSE…
severity: none
vendor: Linux
product: Linux
affected:
  - >-
    Linux >= 9f2475fe7406b8ef5f97099c4980021344872d9f <
    6e6c2ba9022eb8f9b062c81bdc6fd24c7b4c4c16
  - >-
    Linux >= 9f2475fe7406b8ef5f97099c4980021344872d9f <
    6aa722fca9d2aa1f64094101587f8f4a2f83f6aa
  - >-
    Linux >= 9f2475fe7406b8ef5f97099c4980021344872d9f <
    d7e3fa7d06bf7fcaac186d3c4d635caac166d36c
  - Linux 5.9
published: '2026-09-25'
updated: '2026-09-25'
sourceUpdated: '2026-09-25T11:17:03.200'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2026-97530'
references:
  - url: 'https://git.kernel.org/stable/c/6aa722fca9d2aa1f64094101587f8f4a2f83f6aa'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/6e6c2ba9022eb8f9b062c81bdc6fd24c7b4c4c16'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/d7e3fa7d06bf7fcaac186d3c4d635caac166d36c'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
tags:
  - nvd
  - cve.org
ingestedAt: '2026-09-25T11:06:38.924Z'
---

## Overview

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

scsi: qla2xxx: Fix soft lockup polling continuation IOCB signature

qla27xx_copy_multiple_pkt() and qla27xx_copy_fpin_pkt() poll
rsp_q->ring_ptr->signature for RESPONSE_PROCESSED (0xDEADDEAD) to decide
whether the next continuation IOCB has arrived, spinning on cpu_relax()
without advancing the ring or decrementing the entry count while it has
not. response_t::signature lives at byte offset 60, but a continuation
IOCB (sts_cont_entry_t / struct sts_cont_entry_ext) carries raw FC frame
payload at that offset (data[56..59]). A received frame whose payload
bytes happen to equal 0xDEADDEAD is therefore misread as "not yet
arrived", and the loop spins forever in interrupt/DPC context, causing a
CPU soft lockup.

The poll is also unnecessary: callers of qla27xx_copy_multiple_pkt()
(PT_LS4_UNSOL and the NVMe purls path) already gate on
qla_chk_cont_iocb_avail(), which guarantees all entry_count IOCBs are
present before copying begins. The sibling helper
__qla_copy_purex_to_buffer() already drops the signature poll and relies
on the entry_type == STATUS_CONT_TYPE guard instead.

Remove the signature busy-wait from both helpers, keeping the entry_type
guard, and gate the FPIN path with qla_chk_cont_iocb_avail() so it defers
and re-processes on the next interrupt once all continuation IOCBs have
arrived, mirroring the ELS_AUTH_ELS and PT_LS4_UNSOL arms. With this the
signature field is never read on a continuation IOCB, eliminating the
payload-aliasing lockup.

## Remediation

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