Answer in brief
CVE-2026-89860 records a Unknown severity vulnerability in scsi: qla2xxx: Initialize NVMe abort_work once at submission. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=e473b3074104ee09227cfbba5f872e3ea15dd280 <b403700ac62fbf3c310196386e125879a182efcf || >=e473b3074104ee09227cfbba5f872e3ea15dd280 <6a1b50c4879c2e6a034e8e85f9c055f0eea157c7 || >=e473b3074104ee09227cfbba5f872e3ea15dd280 <67f0d5187c29360388f7e1e503c627ec45d01089 || >=e473b3074104ee09227cfbba5f872e3ea15dd280 <f4aaa4a4e6f1da6f3abfd80e1917bef922287177 || >=e473b3074104ee09227cfbba5f872e3ea15dd280 <7e85f6dbc85616de2172bce8eaf84b387a723cd1 | b403700ac62fbf3c310196386e125879a182efcf, 6a1b50c4879c2e6a034e8e85f9c055f0eea157c7, 67f0d5187c29360388f7e1e503c627ec45d01089, f4aaa4a4e6f1da6f3abfd80e1917bef922287177, 7e85f6dbc85616de2172bce8eaf84b387a723cd1 |
| Linux/Linuxgeneric | 4.17 | Not reported |
Published upstream
Sep 16, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 16, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 16, 2026
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.
Quoted source text, attributed separately from HOL analysis.