# CVE-2026-89844: scsi: qla2xxx: Hold vport_slock for host map update in report ID acquisition

> A race condition in the qla2xxx SCSI driver can corrupt internal data structures, potentially leading to system instability or denial of service.

- **Severity:** High 8.8 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **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-101205, BELL-CVE-2026-89844, DEBIAN-CVE-2026-89844, GHSA-8hj3-p94r-f47v, UBUNTU-CVE-2026-89844

## What is CVE-2026-89844?

CVE-2026-89844 is a high-severity 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: Hold vport_slock for host map update in report ID acquisition

qla24xx_report_id_acquisition() format-1 handling drops vport_slock after
taking the vport reference and then calls qla_update_host_map() without
the lock. That reaches qla_update_vp_map(), which mutates the ha->host_map
btree via btree_insert32()/btree_update32()/btree_remove32() and is
documented to require vport_slock to be held by the caller. Running it
unlocked can race concurrent host_map updates and corrupt the btree.

The format-2 path in the same function already wraps its host_map update
(SET_AL_PA) in vport_slock; the format-1 path is the lone outlier.

Hold vport_slock across the format-1 qla_update_host_map() call to honor
the documented locking contract. The vref_count taken in the loop keeps
the vport valid, so this only adds the missing host_map serialization.

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


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

Apply the vendor's patch.

## Is CVE-2026-89844 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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