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-89845scsi: qla2xxx: Avoid req_q_map double-read in qla2x00_error_entry()

Description

In the Linux kernel, the following vulnerability has been resolved: scsi: qla2xxx: Avoid req_q_map double-read in qla2x00_error_entry() qla2x00_error_entry() reads ha->req_q_map[que] twice: once for the NULL check and again when assigning it to req. The map slot is cleared by qla25xx_free_req_que() (ha->req_q_map[que_id] = NULL under mq_lock) during queue teardown, while the response-queue interrupt that drives qla2x00_error_entry() is still registered (the IRQ is released later in qla25xx_free_rsp_que()). If the slot is set to NULL between the two reads, req becomes NULL and is dereferenced. Read the slot once into req and NULL-check the local before use. mq_lock is a mutex and cannot be taken from interrupt context, so the single read plus local check is the appropriate fix for the reported NULL dereference.

Timeline

  1. ID reserved

    By Linux

  2. · 5 days later

    Published

  3. · 33 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.22% · top 88% of all CVEs (16 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 a6fe35c052c4fdd1e8e21251f14eea0bd4bbd25b – < c845f2597787ef70159a32566669e308b2807a56
    • affected a6fe35c052c4fdd1e8e21251f14eea0bd4bbd25b – < fe04b31e386aee4cc3a18f07462af146037dc389
    • affected a6fe35c052c4fdd1e8e21251f14eea0bd4bbd25b – < 1b995cf4157465357d66ba096e7cdaafab9972e7
    • affected a6fe35c052c4fdd1e8e21251f14eea0bd4bbd25b – < d79376fbd2a076de82c1cd8aa0b600b300c75a44
    • affected a6fe35c052c4fdd1e8e21251f14eea0bd4bbd25b – < 1c90b74e484ba48f31944fe04963d99e01ac3767
    • affected a6fe35c052c4fdd1e8e21251f14eea0bd4bbd25b – < 5dd9bec8004ba93cee8b689bf54ce294f59e5e3c
    • affected a6fe35c052c4fdd1e8e21251f14eea0bd4bbd25b – < 35124cfa9898b2088ee72859e573e0876aff66fc
    • affected a6fe35c052c4fdd1e8e21251f14eea0bd4bbd25b – < deb8abde83a799d2501f3977f6d6051000253f5e
  • Linux · Linux

    • affected 3.4
    • unaffected < 3.4
    • unaffected 5.10.270 – ≤ 5.10.*
    • 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

References8

Sources

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

Badge for a README or a ticket

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

Record last updated .