CVE-2026-97530

Not scored yetLast modified Oct 30, 2026

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.

Metrics

No CVSS score has been published yet.

Affected software

Source: the vendor's advisory (CNA). NVD analysis pending.

VendorProductVersions
LinuxLinux>= 9f2475fe7406b8ef5f97099c4980021344872d9f, < bded2de273c5b0e50e3e23de937260436cd67df2; >= 9f2475fe7406b8ef5f97099c4980021344872d9f, < 70df7f03499046da0d28a58ec8b237ed5dfbd0a7; >= 9f2475fe7406b8ef5f97099c4980021344872d9f, < 428e244dd4066abd40ca1ec525b7aab9a9db8296; >= 9f2475fe7406b8ef5f97099c4980021344872d9f, < 3e58eb888ebf265af937f636d05997c60d2f197c; >= 9f2475fe7406b8ef5f97099c4980021344872d9f, < 6e6c2ba9022eb8f9b062c81bdc6fd24c7b4c4c16; >= 9f2475fe7406b8ef5f97099c4980021344872d9f, < 6aa722fca9d2aa1f64094101587f8f4a2f83f6aa; >= 9f2475fe7406b8ef5f97099c4980021344872d9f, < d7e3fa7d06bf7fcaac186d3c4d635caac166d36c
LinuxLinux5.9

References

Timeline

Published
Sep 25, 2026
Last modified
Oct 30, 2026
NVD status
Received

Related CVEs from 2026

CVE-2026-975317.5In the Linux kernel, the following vulnerability has been resolved: scsi: qla2xxx: Skip vport under deletion in report ID acquisition qla2CVE-2026-97532In the Linux kernel, the following vulnerability has been resolved: scsi: qla2xxx: Null out freed pointers in qla2x00_mem_alloc() error patCVE-2026-97533In the Linux kernel, the following vulnerability has been resolved: x86/mm/pat: Acquire init_mm read lock on attribute changes to avoid UAFCVE-2026-97534In the Linux kernel, the following vulnerability has been resolved: f2fs: accurately adjust free_sections during free_segment_range In freCVE-2026-97535In the Linux kernel, the following vulnerability has been resolved: scsi: qla2xxx: Bound VP index against VP_CTRL IOCB bitmap size The VP CVE-2026-975367.5In the Linux kernel, the following vulnerability has been resolved: scsi: qla2xxx: Fix use-after-free of qpair work on queue teardown The CVE-2026-97537In the Linux kernel, the following vulnerability has been resolved: scsi: qla2xxx: Fix queue teardown NULL dma_free and bitmap locking qlaCVE-2026-97538In the Linux kernel, the following vulnerability has been resolved: hwmon: (asus_rog_ryujin) Validate HID report lengths rog_ryujin_raw_evCVE-2026-97539In the Linux kernel, the following vulnerability has been resolved: usb: xusbatm: don't rely on id table pointer arithmetic The current coCVE-2026-97546.5An authenticated user with the read role may read limited amounts of uninitialized stack memory via specially-crafted issuances of the filemCVE-2026-97540In the Linux kernel, the following vulnerability has been resolved: net: usb: pegasus: don't rely on id table pointer arithmetic The curreCVE-2026-97541In the Linux kernel, the following vulnerability has been resolved: wifi: ath9k_htc: don't store usb_device_id usb_device_id is not guaran
CVE-2026-97530: Unscored | Vulnix