CVE-2026-89845

scsi: qla2xxx: Avoid req_q_map double-read in qla2x00_error_entry()

N/A
Published: September 16, 2026 at 10:31 AM UTC
Updated: October 19, 2026 at 09:18 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: scsi: qla2xxx: Avoid req_q_map double-read in qla2x00_error_entry() qla2x00_error_entry() reads ha->req_q_map[que] twice: once for the NULL check and again when assigning it to req. The map slot is cleared by qla25xx_free_req_que() (ha->req_q_map[que_id] = NULL under mq_lock) during queue teardown, while the response-queue interrupt that drives qla2x00_error_entry() is still registered (the IRQ is released later in qla25xx_free_rsp_que()). If the slot is set to NULL between the two reads, req becomes NULL and is dereferenced. Read the slot once into req and NULL-check the local before use. mq_lock is a mutex and cannot be taken from interrupt context, so the single read plus local check is the appropriate fix for the reported NULL dereference.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

3.4a6fe35c052c4fdd1e8e21251f14eea0bd4bbd25b
Vendor states this is fixed in 1b995cf4157465357d66ba096e7cdaafab9972e7 (fixed)
Vendor states this is fixed in 1c90b74e484ba48f31944fe04963d99e01ac3767 (fixed)
Vendor states this is fixed in 35124cfa9898b2088ee72859e573e0876aff66fc (fixed)
Vendor states this is fixed in 5dd9bec8004ba93cee8b689bf54ce294f59e5e3c (fixed)
Vendor states this is fixed in c845f2597787ef70159a32566669e308b2807a56 (fixed)
Vendor states this is fixed in d79376fbd2a076de82c1cd8aa0b600b300c75a44 (fixed)
Vendor states this is fixed in deb8abde83a799d2501f3977f6d6051000253f5e (fixed)
Vendor states this is fixed in fe04b31e386aee4cc3a18f07462af146037dc389 (fixed)
Vendor states this is fixed in 3.4 (unaffected)
Vendor states this is fixed in 5.10.270 (unaffected)
Vendor states this is fixed in 5.15.221 (unaffected)
Vendor states this is fixed in 6.1.188 (unaffected)
Vendor states this is fixed in 6.12.110 (unaffected)
Vendor states this is fixed in 6.18.51 (unaffected)
Vendor states this is fixed in 6.6.157 (unaffected)
Vendor states this is fixed in 7.2.5 (unaffected)
Vendor states this is fixed in 7.3 (unaffected)
Vendor states this is fixed in 7.3-rc1 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card