CVE Intelligence
Unknown

CVE-2026-89845 — scsi: qla2xxx: Avoid req_q_map double-read in qla2x00_error_entry()

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.

Published Sep 16, 2026 · Updated Oct 19, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP, GitHub Security Advisories · CNA: Linux

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • EPSS 0.2% (30-day exploitation probability)+2

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
0.21%
ahead of 11% of scored CVEs · Oct 20, 2026
Affects
Linux
Linux
CVSS base
—
Score not published yet.

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
  2. No fix documented in the sources: reduce exposure and monitor the vendor advisory.
  3. Search available logs for exploit probes, errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Linux Linux ≥ a6fe35c052c4fdd1e8e21251f14eea0bd4bbd25b and < c845f2597787ef70159a32566669e308b2807a56≥ a6fe35c052c4fdd1e8e21251f14eea0bd4bbd25b and < fe04b31e386aee4cc3a18f07462af146037dc389≥ a6fe35c052c4fdd1e8e21251f14eea0bd4bbd25b and < 1b995cf4157465357d66ba096e7cdaafab9972e7≥ a6fe35c052c4fdd1e8e21251f14eea0bd4bbd25b and < d79376fbd2a076de82c1cd8aa0b600b300c75a44≥ a6fe35c052c4fdd1e8e21251f14eea0bd4bbd25b and < 1c90b74e484ba48f31944fe04963d99e01ac3767≥ a6fe35c052c4fdd1e8e21251f14eea0bd4bbd25b and < 5dd9bec8004ba93cee8b689bf54ce294f59e5e3c≥ a6fe35c052c4fdd1e8e21251f14eea0bd4bbd25b and < 35124cfa9898b2088ee72859e573e0876aff66fc≥ a6fe35c052c4fdd1e8e21251f14eea0bd4bbd25b and < deb8abde83a799d2501f3977f6d6051000253f5e
and 1 more version 3.4
Vulnerable CVE Program (cve.org) e CISA ADP

EPSS over time FIRST

Oct 15, 2026 → Oct 20, 2026 · 5 reading(s) · max 0.21%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Not enough vector or weakness data: use the affected application’s logs as a starting point.
application logs

Timeline

What happened to this CVE, newest first.

  • 2026
  • Record published
    Oct 15, 2026
  • Affected products added · linux/linux
    Oct 15, 2026 · CVE Program (cve.org) e CISA ADP
  • Source status changed · → Received
    Oct 15, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 15, 2026 · NIST National Vulnerability Database
  • CVE published
    Sep 16, 2026 · Linux

Source activity

Repeated readings are counted rather than listed.

  • 1× References added · Oct 19, 2026 – Oct 19, 2026
  • 1× Official description updated · Oct 15, 2026 – Oct 15, 2026

References

10 on the record

Elsewhere on this site

Linux
every CVE for this vendor

Related CVEs (same products)

  • Unknown CVE-2026-98866 sched/cache: Introduce task_struct->sched_cache_grp to fix UAF 2d
  • Unknown CVE-2026-98867 dm-pcache: bound the logical key offset from persistent memory 2d
  • Unknown CVE-2026-98868 dm-pcache: reject a kset that overruns its segment 2d
  • Unknown CVE-2026-98856 kprobes: Skip disarmed probes when checking optkprobe overlap 2d
  • Unknown CVE-2026-98857 ipvs: bound LBLCR and LBLC cache growth 2d
  • Unknown CVE-2026-98858 io_uring: fix task_work add use-after-free with SQPOLL 2d

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No CVSS score published by NVD, the CNA, CISA or GitHub so far.
  • No fixed version, patch or mitigation documented.
  • No CISA SSVC assessment.
  • No CWE classification.
  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-89845 is "scsi: qla2xxx: Avoid req_q_map double-read in qla2x00_error_entry()", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. EPSS 0.21% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.