# CVE-2026-89859: scsi: qla2xxx: Zero dport diagnostics buffer to avoid info leak

> A local attacker can read uninitialized kernel heap memory via the qla2xxx SCSI driver diagnostics interface, 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:** 21 Oct 2026
- **Also known as:** AZL-101171, BELL-CVE-2026-89859, DEBIAN-CVE-2026-89859, GHSA-77jx-g549-23wh, UBUNTU-CVE-2026-89859

## What is CVE-2026-89859?

CVE-2026-89859 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 dport diagnostics buffer to avoid info leak

qla2x00_do_dport_diagnostics() allocates the qla_dport_diag response
buffer with kmalloc_obj() (non-zeroing) and, on success, copies the full
sizeof(*dd) back to user space via sg_copy_from_buffer(). The inbound
sg_copy_to_buffer() only fills as many bytes as the user request payload
provides, and qla26xx_dport_diagnostics() zeroes only dd->buf. The
options and unused[] fields are therefore copied out uninitialized,
leaking kernel heap contents to user space.

Allocate with kzalloc_obj(), matching qla2x00_do_dport_diagnostics_v2().

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


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

Apply the vendor's patch.

## Is CVE-2026-89859 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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