Look up another CVE · open CVE-2026-89857 in the interactive tracker
CVE-2026-89857
scsi: qla2xxx: Hold qpair lock when sending NVMe LS reject
Published 2026-09-16 (33 days ago) by the Linux kernel CNA. Subsystem drivers/scsi. Debian urgency: unimportant.
What to do, per Debian release
Debian's own status for CVE-2026-89857 in every release this site tracks, and what each one means in practice. Every status below is the one the Debian Security Team publishes for this CVE. source
| Release | Status | Version | What this means |
|---|---|---|---|
| Debian 12bookworm | not affected | 6.1.190-1 | Nothing to do. bookworm never shipped the vulnerable code. |
| Debian 13trixie | fixedDSA-6528-1 · 2026-09-29 · text | 6.12.111-1 | Update the kernel and reboot. DSA-6528-1 shipped the fix on 2026-09-29, in 6.12.111-1. A running kernel keeps the old code until the machine restarts. |
| Debian 14forky | fixed | 7.2.6-1 | Update the kernel and reboot. Fixed in 7.2.6-1. A running kernel keeps the old code until the machine restarts. |
| Debian unstablesid | fixed | 7.2.6-1 | Update the kernel and reboot. Fixed in 7.2.6-1. A running kernel keeps the old code until the machine restarts. |
| Debian 12bookworm · linux-6.12 | fixedDLA-4817-1 · 2026-10-04 · text | 6.12.111-1~deb12u1 | Update the kernel and reboot. DLA-4817-1 shipped the fix on 2026-10-04, in 6.12.111-1~deb12u1. A running kernel keeps the old code until the machine restarts. |
The vulnerability
What the bug is
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.
Where it lives
The fix touches these files. If the subsystem is one you do not use, the practical exposure is lower, though the package is still the vulnerable one.
drivers/scsi/qla2xxx/qla_nvme.c
- What this is
- QLOGIC QLA2XXX FC-SCSI DRIVERMAINTAINERS section matched on drivers/scsi/qla2xxx/ · linux-scsi@vger.kernel.org · Supported
- Kernel module
- qla2xxx
Check it on the machine
grep -w CONFIG_SCSI_QLA_FC /boot/config-$(uname -r)Reads the booted kernel's own configuration, on the machine and nowhere else. =y is built in, =m is a module, and an is not set line means the code is not there.
lsmod | grep -w qla2xxxPrints a line if that module is loaded right now, and nothing if it is not. One that is not loaded can still be loaded later by anything that needs it.
Show whether Debian builds this, per release
Debian builds this, but not on every flavour. At least one release below builds the code on some of its kernel flavours and not on others, so the answer depends on the architecture and flavour installed.
- bookwormMnot built on amd64/cloud-amd64, arm64/cloud-arm64, armhf/armmp, armhf/armmp-lpae, armhf/rt/armmp
- trixieMnot built on amd64/cloud-amd64, arm64/cloud-arm64, armel/rpi, armhf/armmp, armhf/armmp-lpae, armhf/rt/armmp, s390x/s390x
- forky, sidMnot built on amd64/cloud-amd64, arm64/cloud-arm64, armhf/armmp, armhf/armmp-lpae, s390x/s390x
- bookworm · linux-6.12Mnot built on amd64/cloud-amd64, arm64/cloud-arm64, armhf/armmp, armhf/armmp-lpae, armhf/rt/armmp
- M
- a module where it is built at all; some flavours do not build it
- Build switch
- CONFIG_SCSI_QLA_FC
From the configuration Debian publishes for every kernel flavour it builds. It covers only the architectures Debian ships a linux-config package for, and nothing about a kernel you built yourself. Debian's own status above stays authoritative about the source package.MAINTAINERS kbuild Makefiles Debian linux-config packages
Signals
- Published
- 2026-09-16 (33 days ago)source
- CVSS
- 9.8 critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:Hsource recompute it - Attack vector
- network (AV:N)source
- EPSS
- 0.62%, higher than 48.5% of all CVEssource
- CISA KEV
- not listedthe KEV catalogue
- Debian urgency
- unimportantsource
- Subsystem
- drivers/scsi
Upstream fixes
The versions the CNA records as introducing and fixing this, and the commit for each. source
| Introduced | Fixed in | Commit |
|---|---|---|
| 6.6 | 6.6.157 | 7eb618877503 |
| 6.6 | 6.12.110 | b3a362466db6 |
| 6.6 | 6.18.51 | 11834e5773e2 |
| 6.6 | 7.2.5 | b02ff132017b |
| 6.6 | 7.3 | f743488e4a20 |
Debian advisories
| Advisory | Date | Shipped to | Debian |
|---|---|---|---|
| DLA-4817-1 | 2026-10-04 | bookworm 6.12.111-1~deb12u1 | tracker |
| DSA-6528-1 | 2026-09-29 | trixie 6.12.111-1 | tracker |
Why the CNA scored it this way
Quoted from the kernel CNA's own scoring file, word for word. A highlighted metric carries the most severe value CVSS v3.1 defines for it, which is what pushes the score up. source
- AV:NAttack vector, network
- Unsolicited NVMe-FC LS frames are posted as PT_LS4_UNSOL and reach qla2xxx_process_purls_pkt and qla_nvme_xmt_ls_rsp from a remote SAN peer. QLogic CNAs speak FCoE and fabrics are stretched via FCIP/inter-fabric routing, so a compromised target delivers those frames over the storage network with no local syscall.
- AC:LAttack complexity, low
- A malicious NVMe-FC peer drives both base_qpair producers: LS that fail nvme_fc_rcv_ls_req or xmt_ls_rsp take unlocked qla_nvme_ls_reject_iocb, while concurrent accepted LS (or host NVMe LS/ELS via qla2x00_start_sp on the same qpair from qla2x00_get_sp) take the locked path. The attacker can flood and retry those frames.
- PR:NPrivileges required, none
- Unsolicited NVMe-FC Link Service frames are handled from a logged-in fabric N_Port with no Linux user, capability, or authentication check on the LS-reject path. FC-SP/EDIF is opt-in; zoning is network access, not privileges on the victim host.
- UI:NUser interaction, none
- The HBA response-queue interrupt, DPC PROCESS_PUREX_IOCB path, and nvme_fc workqueue process unsolicited LS and emit the reject IOCB automatically; no victim mount, open, or other interactive action is required.
- S:UScope, unchanged
- Request-ring producer corruption and any resulting kernel or adapter failure stay inside the host kernel that owns the qla2xxx driver and do not cross a VM, IOMMU, or other separate security-authority boundary.
- C:HConfidentiality impact, high
- Unlocked __qla2x00_alloc_iocbs/qla2x00_start_iocbs racing a locked producer can overwrite one ring slot and doorbell an extra stale slot. Firmware then DMA-executes leftover IOCBs whose addresses and handles may already have been recycled, a use-after-free/DMA-confusion read of kernel or I/O buffers.
- I:HIntegrity impact, high
- The same stale-slot replay and double-doorbell let firmware rewrite recycled DMA buffers or complete the wrong outstanding_cmds handle, including a second scsi_done/sp->done on a reused SRB, which is a kernel write and control-flow hijack primitive rather than only dropped I/O.
- A:HAvailability impact, high
- Corrupted request-ring producer state duplicates or drops commands as the fix describes, desynchronizes firmware completions, and can oops on a bad handle or hang NVMe/SCSI I/O, taking down storage served by the adapter.