scsi: qla2xxx: Fix response queue over-consumption in __qla_consume_iocb()
Summary
| CVE | CVE-2026-93242 |
|---|
| State | PUBLISHED |
|---|
| Assigner | Linux |
|---|
| Source Priority | CVE Program / NVD first with legacy fallback |
|---|
| Published | 2026-09-24 16:17:20 UTC |
|---|
| Updated | 2026-09-24 16:17:20 UTC |
|---|
| 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(). |
|---|
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|
| CNA |
Linux |
Linux |
affected fac2807946c10b9a509b9c348afd442fa823c5f7 a136c311676fd1010b1bde3bcfd410caa2fa040f git |
Not specified |
| CNA |
Linux |
Linux |
affected fac2807946c10b9a509b9c348afd442fa823c5f7 d841707fafba5f80341b82e8c3a4c24fc5aa5132 git |
Not specified |
| CNA |
Linux |
Linux |
affected fac2807946c10b9a509b9c348afd442fa823c5f7 6e3f129538c32d0019437197735912308c161843 git |
Not specified |
| CNA |
Linux |
Linux |
affected fac2807946c10b9a509b9c348afd442fa823c5f7 bd1534d4afab47f13dfc27fff6f59dd859a0ac3a git |
Not specified |
| CNA |
Linux |
Linux |
affected fac2807946c10b9a509b9c348afd442fa823c5f7 31715d1e1cbf3a37ce3452635c5602f73fd7abd4 git |
Not specified |
| CNA |
Linux |
Linux |
affected fac2807946c10b9a509b9c348afd442fa823c5f7 df86c27cf1ba9d66f737a1fa56479c6e7efafe4e git |
Not specified |
| CNA |
Linux |
Linux |
affected fac2807946c10b9a509b9c348afd442fa823c5f7 3ba019bdd89d931499d9476456b5d9c7ab7fa753 git |
Not specified |
| CNA |
Linux |
Linux |
affected 5.15 |
Not specified |
| CNA |
Linux |
Linux |
unaffected 5.15 semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 5.15.221 5.15.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.1.188 6.1.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.6.157 6.6.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.12.110 6.12.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.18.51 6.18.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.2.5 7.2.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.3-rc1 * original_commit_for_fix |
Not specified |
References
| Reference | Source | Link | Tags |
|---|
| git.kernel.org/stable/c/df86c27cf1ba9d66f737a1fa56479c6e7efafe4e |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/6e3f129538c32d0019437197735912308c161843 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/a136c311676fd1010b1bde3bcfd410caa2fa040f |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/31715d1e1cbf3a37ce3452635c5602f73fd7abd4 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/3ba019bdd89d931499d9476456b5d9c7ab7fa753 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/d841707fafba5f80341b82e8c3a4c24fc5aa5132 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/bd1534d4afab47f13dfc27fff6f59dd859a0ac3a |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| CVE Program record |
CVE.ORG |
www.cve.org |
canonical |
| NVD vulnerability detail |
NVD |
nvd.nist.gov |
canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.