Linux
scsi: qla2xxx: Hold qpair lock when sending NVMe LS reject
In the Linux kernel, the following vulnerability has been resolved: scsi: qla2xxx: Hold qpair lock when sending NVMe LS reject qla_nvme_ls_reject_iocb() allocates from and advances the request ring through __qla2x00_alloc_iocbs() (which assumes the hardware_lock is held) and qla2x00_start_iocbs() (which advances the ring and rings the request-in doorbell), but takes no lock itself. Two of its callers invoke it without the producer lock held: - qla_nvme_xmt_ls_rsp(), the NVMe-FC .xmt_ls_rsp transport callback, on its error path, and - qla2xxx_process_purls_pkt(), run from the purex work/DPC context. Both use ha->base_qpair, whose qp_lock_ptr is hardware_lock, so they can run concurrently with normal I/O submission on the base ring and corrupt the ring producer state, leading to duplicated or dropped commands. The third caller, qla2xxx_process_purls_iocb(), runs inside qla24xx_process_response_queue() with the qpair lock already held and is safe; that is also why the lock cannot be taken inside the helper itself (it would recursively re-acquire hardware_lock on the response path). Take qp_lock_ptr around the two unlocked callers and document the helper as caller-locked. Both run in process context, so spin_lock_irqsave() is used and nothing in the locked region sleeps.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 875386b98857822b77ac7f95bdf367b70af5b78c, < 7eb618877503edbf17aa65e357a81bda1fc8f163
- >= 875386b98857822b77ac7f95bdf367b70af5b78c, < b3a362466db6b8ec47cc537ac641ac197fa69b5d
- >= 875386b98857822b77ac7f95bdf367b70af5b78c, < 11834e5773e20fd3742d7eb900876e66b9e7d029
- >= 875386b98857822b77ac7f95bdf367b70af5b78c, < b02ff132017b28222187ebcf95ce7f4cb576cd36
- >= 875386b98857822b77ac7f95bdf367b70af5b78c, < f743488e4a203049f27ec5d8cd0caccc483af01e
Fixed in 7eb618877503edbf17aa65e357a81bda1fc8f163, b3a362466db6b8ec47cc537ac641ac197fa69b5d, 11834e5773e20fd3742d7eb900876e66b9e7d029, b02ff132017b28222187ebcf95ce7f4cb576cd36, f743488e4a203049f27ec5d8cd0caccc483af01e
- 6.6
Fixed in 0, 6.6.157, 6.12.110, 6.18.51, 7.2.5, 7.3
Mitigation
Upgrade Linux to 7eb618877503edbf17aa65e357a81bda1fc8f163 or b3a362466db6b8ec47cc537ac641ac197fa69b5d or 11834e5773e20fd3742d7eb900876e66b9e7d029 or b02ff132017b28222187ebcf95ce7f4cb576cd36 or f743488e4a203049f27ec5d8cd0caccc483af01e or later.
Upgrade Linux to 0 or 6.6.157 or 6.12.110 or 6.18.51 or 7.2.5 or 7.3 or later.
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.