CVE-2026-89865

scsi: qla2xxx: Zero SFP DMA buffer in FRU/I2C bsg handlers

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 SFP DMA buffer in FRU/I2C bsg handlers The FRU and I2C bsg handlers stage their transfer in a DMA_POOL_SIZE (256-byte) bounce buffer obtained from dma_pool_alloc(), which does not zero the allocation. They initialize only a few leading bytes before handing the buffer to qla2x00_write_sfp(). qla2x00_write_sfp() can override the transfer length with a user-supplied value: if (len == 1) opt |= BIT_0; if (opt & BIT_0) len = *sfp; *sfp is the first byte of the (user-controlled) payload, so len can grow up to 255. The device then DMA-reads len bytes from the 256-byte pool buffer. Since only a small prefix was written (e.g. MAX_FRU_SIZE == 36 bytes for a FRU version, one byte for a FRU status register), the hardware reads past the initialized region and writes up to ~219 bytes of stale DMA-pool heap memory to the device flash. Allocate the buffer with dma_pool_zalloc() in all five FRU/I2C handlers so any bytes beyond the initialized data are zero rather than stale heap contents.

Affected

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

3.2697a4bc69159c3396035b0506ffa55c4b2d0b1f4
Vendor states this is fixed in 09703bc7c0be3a7a155b0ff5f21f6765ba3f519c (fixed)
Vendor states this is fixed in 581590f560b74399151b3cbc88574424c2f3d2dc (fixed)
Vendor states this is fixed in 84bde5ce4038d9ad811e5c994305bbfcbd7a9f79 (fixed)
Vendor states this is fixed in 97c45c75f5cdec96b1a4fba8b1d55d0dd01af1e8 (fixed)
Vendor states this is fixed in a476377a66897549dd49bee319f4df66623417b7 (fixed)
Vendor states this is fixed in a5501c42256235523c4dddf799f032dfbf4f4c77 (fixed)
Vendor states this is fixed in b157256c28086c434afd70cc78bf9b4d8caf1276 (fixed)
Vendor states this is fixed in b47d4a1547d9ef21b2e9d1a739fe2204d4be05dc (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