CVE-2026-89842scsi: qla2xxx: Skip NVMe LS reject IOCB when FW not started
Updated under an hour ago ()
Does this affect you?
It affects Linux. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
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().
- CVSS
- Not yet scored
- Weakness (CWE)
- Not given
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- Linux
- NVD analysis
- Received
- Record last updated
- Oct 19, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
Linux Linux linux:linux (from the name) | 875386b98857822b77ac7f95bdf367b70af5b78c builds before 2935b730211c5c1433aa6101fa3b55df2b63869a; 875386b98857822b77ac7f95bdf367b70af5b78c builds before 7c1fc75dd3fb6b6414508fbdf7aeed0d757c9120; from 875386b98857822b77ac7f95bdf367b70af5b78c before ac4b019ac07844d3f67ea5e48b1d982b2170d1a7; from 875386b98857822b77ac7f95bdf367b70af5b78c before e9bfb56e2c1bda49d3c5442d824569d71eec07e2; from 875386b98857822b77ac7f95bdf367b70af5b78c before f7e46ebffc5781aab3f1f5a5d4350addbb5833f4 | CNA record |
References
- https://git.kernel.org/stable/c/2935b730211c5c1433aa6101fa3b55df2b63869a
- https://git.kernel.org/stable/c/7c1fc75dd3fb6b6414508fbdf7aeed0d757c9120
- https://git.kernel.org/stable/c/ac4b019ac07844d3f67ea5e48b1d982b2170d1a7
- https://git.kernel.org/stable/c/e9bfb56e2c1bda49d3c5442d824569d71eec07e2
- https://git.kernel.org/stable/c/f7e46ebffc5781aab3f1f5a5d4350addbb5833f4
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.