Answer in brief
CVE-2026-89842 records a Unknown severity vulnerability in scsi: qla2xxx: Skip NVMe LS reject IOCB when FW not started. 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 | >=875386b98857822b77ac7f95bdf367b70af5b78c <2935b730211c5c1433aa6101fa3b55df2b63869a || >=875386b98857822b77ac7f95bdf367b70af5b78c <7c1fc75dd3fb6b6414508fbdf7aeed0d757c9120 || >=875386b98857822b77ac7f95bdf367b70af5b78c <ac4b019ac07844d3f67ea5e48b1d982b2170d1a7 || >=875386b98857822b77ac7f95bdf367b70af5b78c <e9bfb56e2c1bda49d3c5442d824569d71eec07e2 || >=875386b98857822b77ac7f95bdf367b70af5b78c <f7e46ebffc5781aab3f1f5a5d4350addbb5833f4 | 2935b730211c5c1433aa6101fa3b55df2b63869a, 7c1fc75dd3fb6b6414508fbdf7aeed0d757c9120, ac4b019ac07844d3f67ea5e48b1d982b2170d1a7, e9bfb56e2c1bda49d3c5442d824569d71eec07e2, f7e46ebffc5781aab3f1f5a5d4350addbb5833f4 |
| Linux/Linuxgeneric | 6.6 | Not reported |
Published upstream
Sep 16, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 19, 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: Skip NVMe LS reject IOCB when FW not started qla_nvme_xmt_ls_rsp() bails out to the out: label when firmware is not started (!ha->flags.fw_started), but the out: path unconditionally calls qla_nvme_ls_reject_iocb(), which ends in qla2x00_start_iocbs() and an unconditional doorbell write to the request queue in-pointer register. This rings the firmware doorbell and queues an IOCB that stopped or resetting firmware cannot consume, and touches MMIO during the reset/EEH window where fw_started is also clear. Only emit the LS reject IOCB (and ring the doorbell) when fw_started is set; otherwise just clean up and return. The post-allocation failure cases (SRB alloc / qla2x00_start_sp() failure) run with firmware started and still send the reject. Apply the same guard to the reject emission in qla2xxx_process_purls_pkt().
Quoted source text, attributed separately from HOL analysis.