CVE-2026-93242: scsi: qla2xxx: Fix response queue over-consumption in __qla_consume_iocb()
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.23% (FIRST EPSS).
- Fixed version: Linux Linux 31715d1e1cbf3a37ce3452635c5602f73fd7abd4, 3ba019bdd89d931499d9476456b5d9c7ab7fa753, 6e3f129538c32d0019437197735912308c161843; azl3 kernel 6.6.150.1-1 on Azure Linux 3.0 6.6.157.1-1.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 31715d1e1cbf3a37ce3452635c5602f73fd7abd4, 3ba019bdd89d931499d9476456b5d9c7ab7fa753, 6e3f129538c32d0019437197735912308c161843; azl3 kernel 6.6.150.1-1 on Azure Linux 3.0 6.6.157.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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().
- Published
- Sep 24, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.2% · 14th percentile
- CWE
- —
Report tools
Action score
0
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 5.15affected
- fac2807946c10b9a509b9c348afd442fa823c5f7 and later · before a136c311676fd1010b1bde3bcfd410caa2fa040faffected · git
- fac2807946c10b9a509b9c348afd442fa823c5f7 and later · before d841707fafba5f80341b82e8c3a4c24fc5aa5132affected · git
- fac2807946c10b9a509b9c348afd442fa823c5f7 and later · before 6e3f129538c32d0019437197735912308c161843affected · git
- fac2807946c10b9a509b9c348afd442fa823c5f7 and later · before bd1534d4afab47f13dfc27fff6f59dd859a0ac3aaffected · git
- fac2807946c10b9a509b9c348afd442fa823c5f7 and later · before 31715d1e1cbf3a37ce3452635c5602f73fd7abd4affected · git
- fac2807946c10b9a509b9c348afd442fa823c5f7 and later · before df86c27cf1ba9d66f737a1fa56479c6e7efafe4eaffected · git
- fac2807946c10b9a509b9c348afd442fa823c5f7 and later · before 3ba019bdd89d931499d9476456b5d9c7ab7fa753affected · git
- before 5.15not affected · semver
- 5.15.221 and later · up to and including 5.15.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.190-1 | 6.1.190-1 |
| Debian:12 | linux-6.12 | before 6.12.111-1~deb12u1 | 6.12.111-1~deb12u1 |
| Debian:13 | linux | before 6.12.111-1 | 6.12.111-1 |
| Debian:14 | linux | before 7.2.6-1 | 7.2.6-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-93240Sep 24, 2026 · memcg: make the v1 soft limit knob inert0Monitor
- ← EarlierCVE-2026-93241Sep 24, 2026 · memcg: bypass the reclaim and oom killer for dying tasks once oom_reaper is done0Monitor
- Later →CVE-2026-93243Sep 24, 2026 · mm/secretmem: properly account locked pages0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 31715d1e1cbf3a37ce3452635c5602f73fd7abd4 | Vendor (CNA) |
| Linux Linux | 3ba019bdd89d931499d9476456b5d9c7ab7fa753 | Vendor (CNA) |
| Linux Linux | 6e3f129538c32d0019437197735912308c161843 | Vendor (CNA) |
| Linux Linux | a136c311676fd1010b1bde3bcfd410caa2fa040f | Vendor (CNA) |
| Linux Linux | bd1534d4afab47f13dfc27fff6f59dd859a0ac3a | Vendor (CNA) |
| Linux Linux | d841707fafba5f80341b82e8c3a4c24fc5aa5132 | Vendor (CNA) |
| Linux Linux | df86c27cf1ba9d66f737a1fa56479c6e7efafe4e | Vendor (CNA) |
| azl3 kernel 6.6.150.1-1 on Azure Linux 3.0 | 6.6.157.1-1 · Release Notes | Microsoft (MSRC) |
| debian:linux | 6.1.190-1 · Debian:12 | Package registry (OSV) |
| debian:linux | 6.12.111-1 · Debian:13 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.111-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-1181 · Sep 25, 2026(Linux Kernel Güvenlik Bildirimi)
Not on record for this CVE: patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (6 more)Show less
- git.kernel.org/stable/c/3ba019bdd89d931499d9476456b5d9c7ab7fa753
- git.kernel.org/stable/c/6e3f129538c32d0019437197735912308c161843
- git.kernel.org/stable/c/a136c311676fd1010b1bde3bcfd410caa2fa040f
- git.kernel.org/stable/c/bd1534d4afab47f13dfc27fff6f59dd859a0ac3a
- git.kernel.org/stable/c/d841707fafba5f80341b82e8c3a4c24fc5aa5132
- git.kernel.org/stable/c/df86c27cf1ba9d66f737a1fa56479c6e7efafe4e
Vendor advisories and official records. Exploit/PoC links are deliberately left out.