# CVE-2026-89855: scsi: qla2xxx: Serialize flash version read in reset handler

> A race condition in the qla2xxx SCSI driver allows local attackers to corrupt flash register reads, potentially causing data corruption or system instability.

- **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-101513, BELL-CVE-2026-89855, DEBIAN-CVE-2026-89855, GHSA-38m8-7cjw-cwc2, UBUNTU-CVE-2026-89855

## What is CVE-2026-89855?

CVE-2026-89855 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: Serialize flash version read in reset handler

The "update cache versions without reset" sysfs reset operation (0x20261)
calls get_flash_version(), which reads hardware flash registers, without
holding ha->optrom_mutex. The VPD update path serializes the same call
under optrom_mutex, so this reset path can interleave its flash register
accesses with a concurrent VPD or optrom flash operation and corrupt the
reads.

Hold ha->optrom_mutex across the get_flash_version() call to match the
VPD update path.

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


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

Apply the vendor's patch.

## Is CVE-2026-89855 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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