# CVE-2026-89860: scsi: qla2xxx: Initialize NVMe abort_work once at submission

> A race condition in the qla2xxx NVMe driver allows concurrent aborts to corrupt workqueue lists, causing kernel crashes or worker loops.

- **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-101421, BELL-CVE-2026-89860, DEBIAN-CVE-2026-89860, GHSA-hfg3-mcr3-v8r7, UBUNTU-CVE-2026-89860

## What is CVE-2026-89860?

CVE-2026-89860 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: Initialize NVMe abort_work once at submission

qla_nvme_fcp_abort() and qla_nvme_ls_abort() ran INIT_WORK() on
priv->abort_work immediately before schedule_work(). INIT_WORK()
reinitializes the work_struct, resetting its list head and clearing the
pending bit. If an abort is issued more than once for the same command
(for example, concurrent transport teardown and a timeout-driven abort),
the second INIT_WORK() reinitializes a work item that is already queued,
which can corrupt the workqueue list and lead to crashes or a looping
worker.

Initialize priv->abort_work once at command submission, next to the
existing per-command spin_lock_init(&priv->cmd_lock), and leave only
schedule_work() in the abort paths. schedule_work() already does nothing
when the work item is still pending, so a repeated abort no longer
disturbs an in-flight work item. The command is not returned to the
transport until the final kref_put()/release callback runs after
abort_work has completed, so the work item is idle before priv is reused
and the single submission-time INIT_WORK() is safe.

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


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

Apply the vendor's patch.

## Is CVE-2026-89860 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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