CVE-2026-89852

scsi: qla2xxx: Zero mailbox struct in qla2x00_get_firmware_state()

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: Zero mailbox struct in qla2x00_get_firmware_state() The mbx_cmd_t is allocated on the stack but left uninitialized. qla2x00_mailbox_command() has several early-return paths (PCI permanent failure, device failed, EEH busy, ISP abort pending, mailbox access timeout, purge mbox) that return without writing the input mailbox registers back into mcp->mb[]. qla2x00_get_firmware_state() then unconditionally copies mcp->mb[1..6] (and mb[12]) into the caller's states[] array regardless of the return value. On such a failure the copied values are uninitialized kernel stack memory, which is then exposed to userspace via the fw_state and mpi_fw_state sysfs handlers. Zero the mailbox struct so a failed query yields deterministic zeroed state instead of leaking stack contents.

Affected

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

2.6.264d4df1932b6b116aecc81039066fec27f2050762
Vendor states this is fixed in 13d645a2cdb224d27205368f3e3c68bb160daf97 (fixed)
Vendor states this is fixed in 1f49e861c18caf8eef7f0ad9a2c5034f88a6ba79 (fixed)
Vendor states this is fixed in 2f847f06bb223aa895eea91fc9e5e2d6314038eb (fixed)
Vendor states this is fixed in 9efaa782845b4d5fb3e01242be0d06ebc7428d8f (fixed)
Vendor states this is fixed in 9f31de4d07e4cde91dfc24522993a5fbb4d67083 (fixed)
Vendor states this is fixed in e6cfb1ee18336aab41a0941d6d3ea5009aaafc05 (fixed)
Vendor states this is fixed in f29695b1138ae2539c5cd6cdaba9b1b072aaa81a (fixed)
Vendor states this is fixed in f8fc5cc6b3284506c6ab83c822c48133377668bb (fixed)
Vendor states this is fixed in 2.6.26 (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