# CVE-2026-89852: scsi: qla2xxx: Zero mailbox struct in qla2x00_get_firmware_state()

> Local attackers can read uninitialized kernel stack memory via sysfs interfaces in the qla2xxx SCSI driver, potentially exposing sensitive data.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **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-101573, BELL-CVE-2026-89852, DEBIAN-CVE-2026-89852, GHSA-597j-vww4-hxxr, UBUNTU-CVE-2026-89852

## What is CVE-2026-89852?

CVE-2026-89852 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: Zero mailbox struct in qla2x00_get_firmware_state()

The mbx_cmd_t is allocated on the stack but left uninitialized.
qla2x00_mailbox_command() has several early-return paths (PCI permanent
failure, device failed, EEH busy, ISP abort pending, mailbox access
timeout, purge mbox) that return without writing the input mailbox
registers back into mcp->mb[]. qla2x00_get_firmware_state() then
unconditionally copies mcp->mb[1..6] (and mb[12]) into the caller's
states[] array regardless of the return value.

On such a failure the copied values are uninitialized kernel stack
memory, which is then exposed to userspace via the fw_state and
mpi_fw_state sysfs handlers. Zero the mailbox struct so a failed query
yields deterministic zeroed state instead of leaking stack contents.

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


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

Apply the vendor's patch.

## Is CVE-2026-89852 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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