# CVE-2026-90285: scsi: qla2xxx: Remove redundant VPD flash read in sysfs read path

> A race condition in the qla2xxx SCSI driver allows concurrent flash access, potentially leading to 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:** 17 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-102572, BELL-CVE-2026-90285, DEBIAN-CVE-2026-90285, GHSA-gjmh-232w-q2v8, UBUNTU-CVE-2026-90285

## What is CVE-2026-90285?

CVE-2026-90285 is a vulnerability in Linux, published on 17 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: Remove redundant VPD flash read in sysfs read path

qla2x00_sysfs_read_vpd() called ha->isp_ops->read_optrom() a second time
after releasing optrom_mutex. The repeated read is redundant and, unlike
the first, runs without optrom_mutex held, exposing flash access to
concurrent optrom operations. Drop the duplicate call.

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


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

Apply the vendor's patch.

## Is CVE-2026-90285 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-90285 is a vulnerability in Linux, published on 17 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-90285 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-90285/ (Markdown: https://insights.sbomify.com/CVE-2026-90285/index.md)
```

## Sources

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

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