# CVE-2026-93242: scsi: qla2xxx: Fix response queue over-consumption in __qla_consume_iocb()

> A logic error in the qla2xxx SCSI driver causes response queue over-consumption, leading to dropped firmware responses and potential denial of service.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** BELL-CVE-2026-93242, DEBIAN-CVE-2026-93242, GHSA-w8h6-pxw4-jqxh, UBUNTU-CVE-2026-93242

## What is CVE-2026-93242?

CVE-2026-93242 is a denial of service vulnerability in Linux, published on 24 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

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

## Which versions are affected by CVE-2026-93242?


## How do I fix CVE-2026-93242?

Apply the vendor's patch.

## Is CVE-2026-93242 being exploited?

There is no known exploitation of CVE-2026-93242 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-93242 and fix it if it is affected.

What it is: CVE-2026-93242 is a denial of service vulnerability in Linux, published on 24 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-93242 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-93242/ (Markdown: https://insights.sbomify.com/CVE-2026-93242/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-93242
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-93242
- OSV: https://osv.dev/vulnerability/CVE-2026-93242

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-93242/
Summaries are generated and may contain mistakes; the official description above is the record.