# CVE-2026-89843: scsi: qla2xxx: Zero-init bsg stack buffers to avoid info leak

> A local attacker can read uninitialized kernel stack memory via 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-101598, BELL-CVE-2026-89843, DEBIAN-CVE-2026-89843, GHSA-x3rh-x4gx-m2j8, UBUNTU-CVE-2026-89843

## What is CVE-2026-89843?

CVE-2026-89843 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-init bsg stack buffers to avoid info leak

Several bsg handlers stage their request/reply in an uninitialized 256-byte
on-stack buffer (uint8_t bsg[DMA_POOL_SIZE]) and fill it via
sg_copy_to_buffer(), which only copies as many bytes as the user-supplied
request payload. When the request is shorter than the structure, the
remainder of the buffer is left holding stale stack data.

qla2x00_read_fru_status() and qla2x00_read_i2c() then copy the full
structure back to the reply payload with sg_copy_from_buffer(), leaking the
uninitialized stack bytes to user space. The write/update paths do not copy
the buffer back, but can feed uninitialized fields to the device.

Zero the stack buffer at declaration in all five handlers, mirroring the
heap kzalloc() approach, so short requests can no longer expose stale
memory.

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


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

Apply the vendor's patch.

## Is CVE-2026-89843 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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