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

> A race condition in the qla2xxx SCSI driver allows a local attacker to trigger a NULL pointer dereference and kernel crash during queue teardown.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 16 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-101670, BELL-CVE-2026-89845, DEBIAN-CVE-2026-89845, GHSA-rgjv-6vw7-qf84, UBUNTU-CVE-2026-89845

## What is CVE-2026-89845?

CVE-2026-89845 is a vulnerability in Linux, published on 16 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

## Which versions are affected by CVE-2026-89845?


## How do I fix CVE-2026-89845?

Apply the vendor's patch.

## Is CVE-2026-89845 being exploited?

There is no known exploitation of CVE-2026-89845 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-89845 and fix it if it is affected.

What it is: CVE-2026-89845 is a vulnerability in Linux, published on 16 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-89845 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-89845/ (Markdown: https://insights.sbomify.com/CVE-2026-89845/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-89845
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-89845
- OSV: https://osv.dev/vulnerability/CVE-2026-89845

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-89845/
Summaries are generated and may contain mistakes; the official description above is the record.