Look up another CVE · open CVE-2026-89844 in the interactive tracker
CVE-2026-89844
scsi: qla2xxx: Hold vport_slock for host map update in report ID acquisition
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-89844 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
qla24xx_report_id_acquisition() format-1 handling drops vport_slock after taking the vport reference and then calls qla_update_host_map() without the lock. That reaches qla_update_vp_map(), which mutates the ha->host_map btree via btree_insert32()/btree_update32()/btree_remove32() and is documented to require vport_slock to be held by the caller. Running it unlocked can race concurrent host_map updates and corrupt the btree. The format-2 path in the same function already wraps its host_map update (SET_AL_PA) in vport_slock; the format-1 path is the lone outlier. Hold vport_slock across the format-1 qla_update_host_map() call to honor the documented locking contract. The vref_count taken in the loop keeps the vport valid, so this only adds the missing host_map serialization.
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_mbx.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
- 8.8 high
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:Hsource recompute it - Attack vector
- adjacent network (AV:A)source
- EPSS
- 0.34%, higher than 25.6% 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.3 | 6.6.157 | e8f1b0cb9782 |
| 6.3 | 6.12.110 | 6ed66e2a67bb |
| 6.3 | 6.18.51 | 776e4e8cbcf1 |
| 6.3 | 7.2.5 | 7d0b3f745efb |
| 6.3 | 7.3 | 7944039ba9cb |
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:AAttack vector, adjacent network
- qla24xx_report_id_acquisition() runs from qla2xxx response and ATIO interrupt paths when firmware reports NPIV N_Port ID acquisition or VP_STAT_ID_CHG after fabric FDISC. A peer or switch on the same Fibre Channel SAN can drive those events; FC is a non-routable fabric, so Adjacent is the highest defensible vector.
- AC:LAttack complexity, low
- A fabric attacker can bounce the link or induce ID changes so multiple NPIV ports re-acquire IDs while the ATIO MSI-X path (atio_lock) and the response-queue path both call qla_update_host_map() on the shared ha->host_map btree. The attacker drives both sides of that race and can retry at fabric-event rate.
- PR:NPrivileges required, none
- Report-ID IOCBs are firmware completions of unauthenticated Fibre Channel fabric login and ID assignment. The path checks no Linux credentials or capabilities on the victim host; FC-SP/EDIF is opt-in and not required.
- UI:NUser interaction, none
- Host-map updates run automatically in interrupt context when the HBA logs NPIV ports into the fabric or the fabric changes a VP ID. No user or administrator action such as mounting a device is required.
- S:UScope, unchanged
- Concurrent btree mutation corrupts qla2xxx host-map and kernel heap state inside the same host kernel security authority. This is not a VM escape, IOMMU bypass, or other cross-boundary impact.
- C:HConfidentiality impact, high
- Unlocked btree_insert32/update32/remove32 on ha->host_map can free or reuse btree nodes while another CPU walks them, and the tree stores scsi_qla_host pointers consumed by qla_find_host_by_d_id(). That is UAF-class heap corruption enabling kernel memory disclosure.
- I:HIntegrity impact, high
- The same unlocked btree mutation can corrupt node pointers, double-free mempool objects via btree_shrink(), and install attacker-influenced scsi_qla_host pointers used to dispatch incoming FCP/ATIO commands, yielding write and control-flow primitives.
- A:HAvailability impact, high
- lib/btree.c BUG_ON()s on inconsistent nodes, and a corrupted host_map causes oopses in interrupt context when ATIO or response processing dereferences a bad vha pointer, panicking the storage host.