CVE-2026-89857scsi: qla2xxx: Hold qpair lock when sending NVMe LS reject
- 9.8CriticalCVSS base score
- 0.62%Exploitation in 30 daysEPSS · top 50% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
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.
Timeline
ID reserved
By Linux
- 5 days later
· 5 days later
Published
- 33 days later
· 33 days later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | Critical9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVDNVD · Received | 3.1 | Critical9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
- EPSS (exploitation in 30 days)
- 0.62% · top 50% of all CVEs (18 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Critical 9.8.
Affected products
- affected 875386b98857822b77ac7f95bdf367b70af5b78c – < 7eb618877503edbf17aa65e357a81bda1fc8f163
- affected 875386b98857822b77ac7f95bdf367b70af5b78c – < b3a362466db6b8ec47cc537ac641ac197fa69b5d
- affected 875386b98857822b77ac7f95bdf367b70af5b78c – < 11834e5773e20fd3742d7eb900876e66b9e7d029
- affected 875386b98857822b77ac7f95bdf367b70af5b78c – < b02ff132017b28222187ebcf95ce7f4cb576cd36
- affected 875386b98857822b77ac7f95bdf367b70af5b78c – < f743488e4a203049f27ec5d8cd0caccc483af01e
- affected 6.6
- unaffected < 6.6
- unaffected 6.6.157 – ≤ 6.6.*
- unaffected 6.12.110 – ≤ 6.12.*
- unaffected 6.18.51 – ≤ 6.18.*
- unaffected 7.2.5 – ≤ 7.2.*
- unaffected 7.3 – ≤ *
References
References5
- https://git.kernel.org/stable/c/7eb618877503edbf17aa65e357a81bda1fc8f163 (opens in a new tab)
- https://git.kernel.org/stable/c/b3a362466db6b8ec47cc537ac641ac197fa69b5d (opens in a new tab)
- https://git.kernel.org/stable/c/11834e5773e20fd3742d7eb900876e66b9e7d029 (opens in a new tab)
- https://git.kernel.org/stable/c/b02ff132017b28222187ebcf95ce7f4cb576cd36 (opens in a new tab)
- https://git.kernel.org/stable/c/f743488e4a203049f27ec5d8cd0caccc483af01e (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-80457 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-89857)Record last updated .