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().
Fix
Nothing published yet: no patch, vendor advisory or mitigation reference on NVD, no vendor advisory in the News for this CVE, not in CISA's KEV, no fixed package version. BaselineWatch does not guess at one.
Change history 2
- StatusReceived → PublishedNVD modified 2026-10-19 09:07
- First seenunscoredNVD modified 2026-10-19 10:17
Affected (CPE criteria) 0
NVD has not attached CPE configurations yet.
References 7
- https://git.kernel.org/stable/c/31715d1e1cbf3a37ce3452635c5602f73fd7abd4
- https://git.kernel.org/stable/c/3ba019bdd89d931499d9476456b5d9c7ab7fa753
- https://git.kernel.org/stable/c/6e3f129538c32d0019437197735912308c161843
- https://git.kernel.org/stable/c/a136c311676fd1010b1bde3bcfd410caa2fa040f
- https://git.kernel.org/stable/c/bd1534d4afab47f13dfc27fff6f59dd859a0ac3a
- https://git.kernel.org/stable/c/d841707fafba5f80341b82e8c3a4c24fc5aa5132
- https://git.kernel.org/stable/c/df86c27cf1ba9d66f737a1fa56479c6e7efafe4e