Vulnerability · Published Sep 25, 2026 · Assigned by Linux

CVE-2026-97530scsi: qla2xxx: Fix soft lockup polling continuation IOCB signature

Unrated

In plain English

A security flaw in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.2% (higher than 12% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS )–Not rated
Exploit odds (30 days)0.2%top 88.5% of all CVEs
Exploited in the wildNo reportsnot in CISA KEV
Attack toolingNoneno public tooling known

Official description

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.

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Debian:12linuxno fix listedDEBIAN-CVE-2026-97530
Debian:13linux6.12.113-1DEBIAN-CVE-2026-97530
Debian:14linux7.2.7-1DEBIAN-CVE-2026-97530
Debian:12linux-6.126.12.113-1~deb12u1DEBIAN-CVE-2026-97530
Ubuntu:22.04:LTSlinuxno fix listedUBUNTU-CVE-2026-97530
Ubuntu:24.04:LTSlinuxno fix listedUBUNTU-CVE-2026-97530
Ubuntu:26.04:LTSlinux7.0.0-42.42UBUNTU-CVE-2026-97530
Ubuntu:22.04:LTSlinux-allwinner-5.19no fix listedUBUNTU-CVE-2026-97530
Ubuntu:22.04:LTSlinux-awsno fix listedUBUNTU-CVE-2026-97530
Ubuntu:24.04:LTSlinux-awsno fix listedUBUNTU-CVE-2026-97530
Ubuntu:26.04:LTSlinux-aws7.0.0-1016.17UBUNTU-CVE-2026-97530
Ubuntu:22.04:LTSlinux-aws-5.19no fix listedUBUNTU-CVE-2026-97530
Ubuntu:24.04:LTSlinux-aws-6.14no fix listedUBUNTU-CVE-2026-97530
Ubuntu:24.04:LTSlinux-aws-6.17no fix listedUBUNTU-CVE-2026-97530
Ubuntu:22.04:LTSlinux-aws-6.2no fix listedUBUNTU-CVE-2026-97530
Ubuntu:22.04:LTSlinux-aws-6.5no fix listedUBUNTU-CVE-2026-97530
Ubuntu:22.04:LTSlinux-aws-6.8no fix listedUBUNTU-CVE-2026-97530
Ubuntu:24.04:LTSlinux-aws-7.0no fix listedUBUNTU-CVE-2026-97530
Ubuntu:22.04:LTSlinux-azureno fix listedUBUNTU-CVE-2026-97530
Ubuntu:24.04:LTSlinux-azureno fix listedUBUNTU-CVE-2026-97530
Ubuntu:26.04:LTSlinux-azureno fix listedUBUNTU-CVE-2026-97530
Ubuntu:22.04:LTSlinux-azure-5.19no fix listedUBUNTU-CVE-2026-97530
Ubuntu:24.04:LTSlinux-azure-6.11no fix listedUBUNTU-CVE-2026-97530
Ubuntu:24.04:LTSlinux-azure-6.14no fix listedUBUNTU-CVE-2026-97530
Ubuntu:24.04:LTSlinux-azure-6.17no fix listedUBUNTU-CVE-2026-97530
Ubuntu:22.04:LTSlinux-azure-6.2no fix listedUBUNTU-CVE-2026-97530
Ubuntu:22.04:LTSlinux-azure-6.5no fix listedUBUNTU-CVE-2026-97530
Ubuntu:22.04:LTSlinux-azure-6.8no fix listedUBUNTU-CVE-2026-97530
Ubuntu:24.04:LTSlinux-azure-7.0no fix listedUBUNTU-CVE-2026-97530
Ubuntu:22.04:LTSlinux-azure-fdeno fix listedUBUNTU-CVE-2026-97530
Ubuntu:24.04:LTSlinux-azure-fdeno fix listedUBUNTU-CVE-2026-97530
Ubuntu:26.04:LTSlinux-azure-fdeno fix listedUBUNTU-CVE-2026-97530
Ubuntu:22.04:LTSlinux-azure-fde-5.19no fix listedUBUNTU-CVE-2026-97530
Ubuntu:24.04:LTSlinux-azure-fde-6.14no fix listedUBUNTU-CVE-2026-97530
Ubuntu:24.04:LTSlinux-azure-fde-6.17no fix listedUBUNTU-CVE-2026-97530
Ubuntu:22.04:LTSlinux-azure-fde-6.2no fix listedUBUNTU-CVE-2026-97530
Ubuntu:22.04:LTSlinux-azure-fde-6.8no fix listedUBUNTU-CVE-2026-97530
Ubuntu:24.04:LTSlinux-azure-fde-7.0no fix listedUBUNTU-CVE-2026-97530
Ubuntu:24.04:LTSlinux-azure-nvidiano fix listedUBUNTU-CVE-2026-97530
Ubuntu:24.04:LTSlinux-azure-nvidia-6.14no fix listedUBUNTU-CVE-2026-97530
Ubuntu:22.04:LTSlinux-gcpno fix listedUBUNTU-CVE-2026-97530
Ubuntu:24.04:LTSlinux-gcpno fix listedUBUNTU-CVE-2026-97530
Ubuntu:26.04:LTSlinux-gcp7.0.0-1016.18UBUNTU-CVE-2026-97530
Ubuntu:22.04:LTSlinux-gcp-5.19no fix listedUBUNTU-CVE-2026-97530
Ubuntu:24.04:LTSlinux-gcp-6.11no fix listedUBUNTU-CVE-2026-97530
Ubuntu:24.04:LTSlinux-gcp-6.14no fix listedUBUNTU-CVE-2026-97530
Ubuntu:24.04:LTSlinux-gcp-6.17no fix listedUBUNTU-CVE-2026-97530
Ubuntu:22.04:LTSlinux-gcp-6.2no fix listedUBUNTU-CVE-2026-97530
Ubuntu:22.04:LTSlinux-gcp-6.5no fix listedUBUNTU-CVE-2026-97530
Ubuntu:22.04:LTSlinux-gcp-6.8no fix listedUBUNTU-CVE-2026-97530
Ubuntu:24.04:LTSlinux-gcp-7.0no fix listedUBUNTU-CVE-2026-97530
Ubuntu:22.04:LTSlinux-gkeno fix listedUBUNTU-CVE-2026-97530
Ubuntu:24.04:LTSlinux-gkeno fix listedUBUNTU-CVE-2026-97530
Ubuntu:26.04:LTSlinux-gkeno fix listedUBUNTU-CVE-2026-97530
Ubuntu:22.04:LTSlinux-gkeopno fix listedUBUNTU-CVE-2026-97530
Ubuntu:24.04:LTSlinux-gkeopno fix listedUBUNTU-CVE-2026-97530
Ubuntu:22.04:LTSlinux-hwe-5.19no fix listedUBUNTU-CVE-2026-97530
Ubuntu:24.04:LTSlinux-hwe-6.11no fix listedUBUNTU-CVE-2026-97530
Ubuntu:24.04:LTSlinux-hwe-6.14no fix listedUBUNTU-CVE-2026-97530
Ubuntu:24.04:LTSlinux-hwe-6.17no fix listedUBUNTU-CVE-2026-97530
Ubuntu:22.04:LTSlinux-hwe-6.2no fix listedUBUNTU-CVE-2026-97530
Ubuntu:22.04:LTSlinux-hwe-6.5no fix listedUBUNTU-CVE-2026-97530
Ubuntu:22.04:LTSlinux-hwe-6.8no fix listedUBUNTU-CVE-2026-97530
Ubuntu:24.04:LTSlinux-hwe-7.07.0.0-42.42~24.04.1UBUNTU-CVE-2026-97530
Ubuntu:22.04:LTSlinux-ibmno fix listedUBUNTU-CVE-2026-97530
Ubuntu:24.04:LTSlinux-ibmno fix listedUBUNTU-CVE-2026-97530
Ubuntu:26.04:LTSlinux-ibm7.0.0-1017.17UBUNTU-CVE-2026-97530
Ubuntu:22.04:LTSlinux-ibm-6.8no fix listedUBUNTU-CVE-2026-97530
Ubuntu:22.04:LTSlinux-intel-iot-realtimeno fix listedUBUNTU-CVE-2026-97530
Ubuntu:22.04:LTSlinux-intel-iotgno fix listedUBUNTU-CVE-2026-97530
Ubuntu:22.04:LTSlinux-kvmno fix listedUBUNTU-CVE-2026-97530
Ubuntu:22.04:LTSlinux-lowlatencyno fix listedUBUNTU-CVE-2026-97530
Ubuntu:24.04:LTSlinux-lowlatencyno fix listedUBUNTU-CVE-2026-97530
Ubuntu:22.04:LTSlinux-lowlatency-hwe-5.19no fix listedUBUNTU-CVE-2026-97530
Ubuntu:24.04:LTSlinux-lowlatency-hwe-6.11no fix listedUBUNTU-CVE-2026-97530
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.2no fix listedUBUNTU-CVE-2026-97530
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.5no fix listedUBUNTU-CVE-2026-97530
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.8no fix listedUBUNTU-CVE-2026-97530
Ubuntu:22.04:LTSlinux-nvidiano fix listedUBUNTU-CVE-2026-97530
Ubuntu:24.04:LTSlinux-nvidiano fix listedUBUNTU-CVE-2026-97530
Ubuntu:26.04:LTSlinux-nvidiano fix listedUBUNTU-CVE-2026-97530
Ubuntu:24.04:LTSlinux-nvidia-6.11no fix listedUBUNTU-CVE-2026-97530
Ubuntu:24.04:LTSlinux-nvidia-6.17no fix listedUBUNTU-CVE-2026-97530
Ubuntu:22.04:LTSlinux-nvidia-6.2no fix listedUBUNTU-CVE-2026-97530
Ubuntu:22.04:LTSlinux-nvidia-6.5no fix listedUBUNTU-CVE-2026-97530
Ubuntu:22.04:LTSlinux-nvidia-6.8no fix listedUBUNTU-CVE-2026-97530
Ubuntu:24.04:LTSlinux-nvidia-7.0no fix listedUBUNTU-CVE-2026-97530
Ubuntu:26.04:LTSlinux-nvidia-bosno fix listedUBUNTU-CVE-2026-97530
Ubuntu:24.04:LTSlinux-nvidia-lowlatencyno fix listedUBUNTU-CVE-2026-97530
Ubuntu:22.04:LTSlinux-nvidia-tegrano fix listedUBUNTU-CVE-2026-97530
Ubuntu:24.04:LTSlinux-nvidia-tegrano fix listedUBUNTU-CVE-2026-97530
Ubuntu:22.04:LTSlinux-nvidia-tegra-igxno fix listedUBUNTU-CVE-2026-97530
Ubuntu:22.04:LTSlinux-oem-5.17no fix listedUBUNTU-CVE-2026-97530
Ubuntu:22.04:LTSlinux-oem-6.0no fix listedUBUNTU-CVE-2026-97530
Ubuntu:22.04:LTSlinux-oem-6.1no fix listedUBUNTU-CVE-2026-97530
Ubuntu:24.04:LTSlinux-oem-6.11no fix listedUBUNTU-CVE-2026-97530
Ubuntu:24.04:LTSlinux-oem-6.14no fix listedUBUNTU-CVE-2026-97530
Ubuntu:24.04:LTSlinux-oem-6.17no fix listedUBUNTU-CVE-2026-97530
Ubuntu:22.04:LTSlinux-oem-6.5no fix listedUBUNTU-CVE-2026-97530
Ubuntu:24.04:LTSlinux-oem-6.8no fix listedUBUNTU-CVE-2026-97530
Ubuntu:26.04:LTSlinux-oem-7.07.0.0-1017.17UBUNTU-CVE-2026-97530
Ubuntu:22.04:LTSlinux-oracleno fix listedUBUNTU-CVE-2026-97530
Ubuntu:24.04:LTSlinux-oracleno fix listedUBUNTU-CVE-2026-97530
Ubuntu:26.04:LTSlinux-oracle7.0.0-1015.16UBUNTU-CVE-2026-97530
Ubuntu:24.04:LTSlinux-oracle-6.14no fix listedUBUNTU-CVE-2026-97530
Ubuntu:24.04:LTSlinux-oracle-6.17no fix listedUBUNTU-CVE-2026-97530
Ubuntu:22.04:LTSlinux-oracle-6.5no fix listedUBUNTU-CVE-2026-97530
Ubuntu:22.04:LTSlinux-oracle-6.8no fix listedUBUNTU-CVE-2026-97530
Ubuntu:24.04:LTSlinux-oracle-7.0no fix listedUBUNTU-CVE-2026-97530
Ubuntu:22.04:LTSlinux-raspino fix listedUBUNTU-CVE-2026-97530
Ubuntu:24.04:LTSlinux-raspino fix listedUBUNTU-CVE-2026-97530
Ubuntu:26.04:LTSlinux-raspino fix listedUBUNTU-CVE-2026-97530
Ubuntu:24.04:LTSlinux-raspi-realtimeno fix listedUBUNTU-CVE-2026-97530
Ubuntu:22.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-97530
Ubuntu:24.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-97530
Ubuntu:26.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-97530
Ubuntu:22.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-97530
Ubuntu:24.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-97530
Ubuntu:26.04:LTSlinux-riscv7.0.0-42.42.1UBUNTU-CVE-2026-97530
Ubuntu:22.04:LTSlinux-riscv-5.19no fix listedUBUNTU-CVE-2026-97530
Ubuntu:24.04:LTSlinux-riscv-6.14no fix listedUBUNTU-CVE-2026-97530
Ubuntu:24.04:LTSlinux-riscv-6.17no fix listedUBUNTU-CVE-2026-97530
Ubuntu:22.04:LTSlinux-riscv-6.5no fix listedUBUNTU-CVE-2026-97530
Ubuntu:22.04:LTSlinux-riscv-6.8no fix listedUBUNTU-CVE-2026-97530
Ubuntu:24.04:LTSlinux-riscv-7.07.0.0-42.42.1~24.04.1UBUNTU-CVE-2026-97530
Ubuntu:22.04:LTSlinux-starfive-5.19no fix listedUBUNTU-CVE-2026-97530
Ubuntu:22.04:LTSlinux-starfive-6.2no fix listedUBUNTU-CVE-2026-97530
Ubuntu:22.04:LTSlinux-starfive-6.5no fix listedUBUNTU-CVE-2026-97530
Ubuntu:24.04:LTSlinux-vmwareno fix listedUBUNTU-CVE-2026-97530
Ubuntu:24.04:LTSlinux-xilinxno fix listedUBUNTU-CVE-2026-97530
Ubuntu:22.04:LTSlinux-xilinx-zynqmpno fix listedUBUNTU-CVE-2026-97530

Affected products (as reported)

VendorProductVersions
Linux Linux 9f2475fe7406b8ef5f97099c4980021344872d9f – before bded2de273c5b0e50e3e23de937260436cd67df29f2475fe7406b8ef5f97099c4980021344872d9f – before 70df7f03499046da0d28a58ec8b237ed5dfbd0a79f2475fe7406b8ef5f97099c4980021344872d9f – before 428e244dd4066abd40ca1ec525b7aab9a9db82969f2475fe7406b8ef5f97099c4980021344872d9f – before 3e58eb888ebf265af937f636d05997c60d2f197c9f2475fe7406b8ef5f97099c4980021344872d9f – before 6e6c2ba9022eb8f9b062c81bdc6fd24c7b4c4c169f2475fe7406b8ef5f97099c4980021344872d9f – before 6aa722fca9d2aa1f64094101587f8f4a2f83f6aa9f2475fe7406b8ef5f97099c4980021344872d9f – before d7e3fa7d06bf7fcaac186d3c4d635caac166d36c
Linux Linux 5.9

References