CVE-2026-89842

CVE CVE-2026-89842EUVD EUVD-2026-80442Published 2026-09-16T10:31:16.000Z

What the advisory describes

In the Linux kernel, the following vulnerability has been resolved: scsi: qla2xxx: Skip NVMe LS reject IOCB when FW not started qla_nvme_xmt_ls_rsp() bails out to the out: label when firmware is not started (!ha->flags.fw_started), but the out: path unconditionally calls qla_nvme_ls_reject_iocb(), which ends in qla2x00_start_iocbs() and an unconditional doorbell write to the request queue in-pointer register. This rings the firmware doorbell and queues an IOCB that stopped or resetting firmware cannot consume, and touches MMIO during the reset/EEH window where fw_started is also clear. Only emit the LS reject IOCB (and ring the doorbell) when fw_started is set; otherwise just clean up and return. The post-allocation failure cases (SRB alloc / qla2x00_start_sp() failure) run with firmware started and still send the reject. Apply the same guard to the reject emission in qla2xxx_process_purls_pkt().

Source: EUVD (ENISA), in the words of the advisory.

Products the advisory names

These come from the advisory itself, not from any check we performed.

Linux — Linux 875386b98857822b77ac7f95bdf367b70af5b78c <e9bfb56e2c1bda49d3c5442d824569d71eec07e2; 875386b98857822b77ac7f95bdf367b70af5b78c <ac4b019ac07844d3f67ea5e48b1d982b2170d1a7; patch: 7.3-rc1; 6.6; 875386b98857822b77ac7f95bdf367b70af5b78c <2935b730211c5c1433aa6101fa3b55df2b63869a; patch: 6.12.110; patch: 7.2.5; patch: 0; patch: 6.6.157; 875386b98857822b77ac7f95bdf367b70af5b78c <7c1fc75dd3fb6b6414508fbdf7aeed0d757c9120; 875386b98857822b77ac7f95bdf367b70af5b78c <f7e46ebffc5781aab3f1f5a5d4350addbb5833f4; patch: 6.18.51

The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.

Carried in the product catalogue

An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.

Linux — Linux

Does this concern one of your customers?

This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.

Try it for 28 days

Patchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.