Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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

Timeline

  1. ID reserved

    By Linux

  2. · 7 days later

    Published

  3. · 25 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.23% · top 86% of all CVEs (18 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected fac2807946c10b9a509b9c348afd442fa823c5f7 – < a136c311676fd1010b1bde3bcfd410caa2fa040f
    • affected fac2807946c10b9a509b9c348afd442fa823c5f7 – < d841707fafba5f80341b82e8c3a4c24fc5aa5132
    • affected fac2807946c10b9a509b9c348afd442fa823c5f7 – < 6e3f129538c32d0019437197735912308c161843
    • affected fac2807946c10b9a509b9c348afd442fa823c5f7 – < bd1534d4afab47f13dfc27fff6f59dd859a0ac3a
    • affected fac2807946c10b9a509b9c348afd442fa823c5f7 – < 31715d1e1cbf3a37ce3452635c5602f73fd7abd4
    • affected fac2807946c10b9a509b9c348afd442fa823c5f7 – < df86c27cf1ba9d66f737a1fa56479c6e7efafe4e
    • affected fac2807946c10b9a509b9c348afd442fa823c5f7 – < 3ba019bdd89d931499d9476456b5d9c7ab7fa753
  • Linux · Linux

    • affected 5.15
    • unaffected < 5.15
    • unaffected 5.15.221 – ≤ 5.15.*
    • unaffected 6.1.188 – ≤ 6.1.*
    • unaffected 6.6.157 – ≤ 6.6.*
    • unaffected 6.12.110 – ≤ 6.12.*
    • unaffected 6.18.51 – ≤ 6.18.*
    • unaffected 7.2.5 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References7

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-93242 badge
[![CVE-2026-93242](https://cveledger.app/badge/CVE-2026-93242.svg)](https://cveledger.app/cve/CVE-2026-93242)

Record last updated .