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

> A logic error in the qla2xxx SCSI driver allows an attacker to hang the adapter by triggering mailbox commands during chip-down states, causing denial of service.

- **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-101382, BELL-CVE-2026-89850, DEBIAN-CVE-2026-89850, GHSA-52m9-92gj-jg2v, UBUNTU-CVE-2026-89850

## What is CVE-2026-89850?

CVE-2026-89850 is a denial of service 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: 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.

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


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

Apply the vendor's patch.

## Is CVE-2026-89850 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-89850 is a denial of service 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-89850 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-89850/ (Markdown: https://insights.sbomify.com/CVE-2026-89850/index.md)
```

## Sources

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

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