CVE-2026-97530

published 25 Sep 2026 · updated 20 Nov 2026

scsi: qla2xxx: Fix soft lockup polling continuation IOCB signature

5.5MediumCVSS 5.5EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel d7e3fa7d06bf7fcaac186d3c4d635caac166d36c, Kernel 3e58eb888ebf265af937f636d05997c60d2f197c, Kernel 428e244dd4066abd40ca1ec525b7aab9a9db8296 and 10 more.

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

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel>=9f2475fe7406b8ef5f97099c4980021344872d9f <d7e3fa7d06bf7fcaac186d3c4d635caac166d36c, >=9f2475fe7406b8ef5f97099c4980021344872d9f <3e58eb888ebf265af937f636d05997c60d2f197c, >=9f2475fe7406b8ef5f97099c4980021344872d9f <428e244dd4066abd40ca1ec525b7aab9a9db8296, >=9f2475fe7406b8ef5f97099c4980021344872d9f <6aa722fca9d2aa1f64094101587f8f4a2f83f6aa, >=9f2475fe7406b8ef5f97099c4980021344872d9f <6e6c2ba9022eb8f9b062c81bdc6fd24c7b4c4c16, >=9f2475fe7406b8ef5f97099c4980021344872d9f <70df7f03499046da0d28a58ec8b237ed5dfbd0a7, >=9f2475fe7406b8ef5f97099c4980021344872d9f <bded2de273c5b0e50e3e23de937260436cd67df2, =5.9d7e3fa7d06bf7fcaac186d3c4d635caac166d36c, 3e58eb888ebf265af937f636d05997c60d2f197c, 428e244dd4066abd40ca1ec525b7aab9a9db8296, 6aa722fca9d2aa1f64094101587f8f4a2f83f6aa, 6e6c2ba9022eb8f9b062c81bdc6fd24c7b4c4c16, 70df7f03499046da0d28a58ec8b237ed5dfbd0a7, bded2de273c5b0e50e3e23de937260436cd67df2
linux-kernel: Kernel>=5.9.0 <5.15.224, >=6.13.0 <6.18.53, >=6.19.0 <7.2.7, >=6.2.0 <6.6.160, >=6.7.0 <6.12.112, >=5.16.0 <6.1.1915.15.224, 6.18.53, 7.2.7, 6.6.160, 6.12.112, 6.1.191

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-97530 severity on Zeptric[![CVE-2026-97530](https://zeptric.io/badge/cve/CVE-2026-97530.svg)](https://zeptric.io/cve/CVE-2026-97530)