CVE-2026-89850

scsi: qla2xxx: Don't query firmware state while chip is down

N/A
Published: September 16, 2026 at 10:31 AM UTC
Updated: October 19, 2026 at 09:18 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: scsi: qla2xxx: Don't query firmware state while chip is down qla2x00_fw_state_show() initializes rval to QLA_FUNCTION_FAILED and jumps to the out: label when the chip is down or EEH is busy. The out: block then re-issued qla2x00_get_firmware_state() because rval != QLA_SUCCESS, defeating the chip-down/EEH-busy guards and issuing a mailbox command (outside optrom_mutex) during ISP reset or PCI error recovery, which can hang the adapter. It also turned a normal in-lock mailbox failure into a second unsynchronized mailbox attempt. Make the out: fallback only mark the firmware state as unknown. The mailbox is now issued at most once, inside optrom_mutex, and only when the chip is up and not EEH-busy.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

4.20b6faaaf796d7bfb00e32ca5c905d55cc43e89448
Vendor states this is fixed in 178d984e8875292582e4295cf559b2b11d3c9325 (fixed)
Vendor states this is fixed in 22f44f77da496bc355479c08a0a9dbc9ad42ba42 (fixed)
Vendor states this is fixed in 7bc2baed8a3d6a1e2a3f6b78d245f25d1e18a749 (fixed)
Vendor states this is fixed in a194684853dceaa1d6b7a9a02bc12f479232ad9b (fixed)
Vendor states this is fixed in a6374b508893de15fee78583a95f5099d7812e85 (fixed)
Vendor states this is fixed in b6a30baa29695fa0eaba4a3a04435a3c1a5cb63d (fixed)
Vendor states this is fixed in cba780c01f72f8585ca81ad7304097f8b12ef339 (fixed)
Vendor states this is fixed in e0cebe20dcffbed9c078fe30e2d18cd5046d9eff (fixed)
Vendor states this is fixed in 4.20 (unaffected)
Vendor states this is fixed in 5.10.270 (unaffected)
Vendor states this is fixed in 5.15.221 (unaffected)
Vendor states this is fixed in 6.1.188 (unaffected)
Vendor states this is fixed in 6.12.110 (unaffected)
Vendor states this is fixed in 6.18.51 (unaffected)
Vendor states this is fixed in 6.6.157 (unaffected)
Vendor states this is fixed in 7.2.5 (unaffected)
Vendor states this is fixed in 7.3 (unaffected)
Vendor states this is fixed in 7.3-rc1 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card