CVE-2026-89843

scsi: qla2xxx: Zero-init bsg stack buffers to avoid info leak

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-init bsg stack buffers to avoid info leak Several bsg handlers stage their request/reply in an uninitialized 256-byte on-stack buffer (uint8_t bsg[DMA_POOL_SIZE]) and fill it via sg_copy_to_buffer(), which only copies as many bytes as the user-supplied request payload. When the request is shorter than the structure, the remainder of the buffer is left holding stale stack data. qla2x00_read_fru_status() and qla2x00_read_i2c() then copy the full structure back to the reply payload with sg_copy_from_buffer(), leaking the uninitialized stack bytes to user space. The write/update paths do not copy the buffer back, but can feed uninitialized fields to the device. Zero the stack buffer at declaration in all five handlers, mirroring the heap kzalloc() approach, so short requests can no longer expose stale memory.

Affected

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

3.2697a4bc69159c3396035b0506ffa55c4b2d0b1f4
Vendor states this is fixed in 1c820d0900e4aacd5020b989159f6b4b2f7d0d6a (fixed)
Vendor states this is fixed in 26bc6a2c235a70bfc9b6de412600208aca820e20 (fixed)
Vendor states this is fixed in 4fe5790674097897a1af1367d1e384f7e5a62fb7 (fixed)
Vendor states this is fixed in 5ab32dff910291b5e6bf6223f8a4003536c1800a (fixed)
Vendor states this is fixed in 708c0ec1e09c52fee24b74ce9398bf3f8d1c83fd (fixed)
Vendor states this is fixed in 7881faf862ee301ecfe3adc0725bd2fa0021cd95 (fixed)
Vendor states this is fixed in 947c6bfcf7f5ec924995bec43e3108b98c75b44e (fixed)
Vendor states this is fixed in b93d3bb3afe1b44489927de1eb4e66e8536a5935 (fixed)
Vendor states this is fixed in 3.2 (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