# CVE-2026-89858: scsi: qla2xxx: Bound image count in qla2x00_update_fru_versions()

> A local attacker can trigger an out-of-bounds read in the qla2xxx SCSI driver to leak kernel stack memory to the device.

- **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-101634, BELL-CVE-2026-89858, DEBIAN-CVE-2026-89858, GHSA-m82c-43pj-6cj6, UBUNTU-CVE-2026-89858

## What is CVE-2026-89858?

CVE-2026-89858 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: Bound image count in qla2x00_update_fru_versions()

qla2x00_update_fru_versions() copies the user-supplied BSG request into
a fixed 256-byte stack buffer (bsg[DMA_POOL_SIZE]) and then iterates
list->count times over the qla_image_version array embedded in that
buffer, advancing the image pointer each iteration. count is taken
directly from user input with no upper bound, while only (DMA_POOL_SIZE
- sizeof(list->count)) / sizeof(struct qla_image_version) = 6 entries
actually fit. A larger count walks the image pointer off the end of the
stack buffer, reading adjacent kernel stack memory and sending it to the
device via qla2x00_write_sfp().

Reject requests whose declared count does not fit in the buffer.

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


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

Apply the vendor's patch.

## Is CVE-2026-89858 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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