scsi: qla2xxx: Skip NVMe LS reject IOCB when FW not started
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
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().
From the CVE record · Linux
The qla2xxx driver can queue an NVMe LS reject IOCB and write to the firmware doorbell even when firmware has not started. This occurs during a firmware stop or reset window, when the firmware cannot consume the IOCB and the driver may touch MMIO. The input does not establish how an attacker could trigger this behavior or whether authentication or user interaction is required.
Engineers running Linux systems that use the qla2xxx driver should check their kernel; affected versions are not specified.