CVE-2026-93242

scsi: qla2xxx: Fix response queue over-consumption in __qla_consume_iocb()

N/A
Published: September 24, 2026 at 03:40 PM UTC
Updated: October 19, 2026 at 10:17 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: Fix response queue over-consumption in __qla_consume_iocb() qla24xx_process_response_queue() advances ring_ptr past the head IOCB before dispatching, so by the time __qla_consume_iocb() runs, ring_ptr already points at the first continuation IOCB. The function however looped purex->entry_count times starting at ring_ptr. As entry_count includes the head, this consumed one entry too many: it stamped RESPONSE_PROCESSED on the next, unrelated IOCB and advanced the ring past it, silently dropping a legitimate firmware response. The head IOCB's signature was also never marked. Mark the head processed and account for it, then consume only the entry_count - 1 continuation IOCBs, matching __qla_copy_purex_to_buffer().

Affected

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

5.15fac2807946c10b9a509b9c348afd442fa823c5f7
Vendor states this is fixed in 31715d1e1cbf3a37ce3452635c5602f73fd7abd4 (fixed)
Vendor states this is fixed in 3ba019bdd89d931499d9476456b5d9c7ab7fa753 (fixed)
Vendor states this is fixed in 6e3f129538c32d0019437197735912308c161843 (fixed)
Vendor states this is fixed in a136c311676fd1010b1bde3bcfd410caa2fa040f (fixed)
Vendor states this is fixed in bd1534d4afab47f13dfc27fff6f59dd859a0ac3a (fixed)
Vendor states this is fixed in d841707fafba5f80341b82e8c3a4c24fc5aa5132 (fixed)
Vendor states this is fixed in df86c27cf1ba9d66f737a1fa56479c6e7efafe4e (fixed)
Vendor states this is fixed in 5.15 (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