# CVE-2026-89861: scsi: qla2xxx: Hold vport reference in qla24xx_report_id_acquisition()

> A use-after-free in the qla2xxx SCSI driver allows attackers to execute arbitrary code or escalate privileges via concurrent vport deallocation.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 16 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-101339, BELL-CVE-2026-89861, DEBIAN-CVE-2026-89861, GHSA-jp2p-cx4h-xhw3, UBUNTU-CVE-2026-89861

## What is CVE-2026-89861?

CVE-2026-89861 is a high-severity use after free vulnerability in Linux, published on 16 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In the Linux kernel, the following vulnerability has been resolved:

scsi: qla2xxx: Hold vport reference in qla24xx_report_id_acquisition()

In the format 1 path, the virtual port is located on ha->vp_list while
holding vport_slock, but the lock is dropped before vp is used:
qla_update_host_map() is called and VP_IDX_ACQUIRED/REGISTER_FC4_NEEDED/
REGISTER_FDMI_NEEDED are set on vp. No reference is taken across that
window, so a concurrent qla24xx_deallocate_vp_id() can tear the vport
down and free it, leading to a use-after-free.

Take a vport reference (vref_count) under vport_slock when the matching
vp is found, and drop it after the last use of
vp. qla24xx_deallocate_vp_id() waits for vref_count to reach zero before
unlinking and freeing the vport, so the pointer stays valid. This
matches the reference idiom already used by the other ha->vp_list
traversals.

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


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

Apply the vendor's patch.

## Is CVE-2026-89861 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-89861 is a high-severity use after free vulnerability in Linux, published on 16 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-89861 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-89861/ (Markdown: https://insights.sbomify.com/CVE-2026-89861/index.md)
```

## Sources

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

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