CVE-2026-89865 scsi: qla2xxx: Zero SFP DMA buffer in FRU/I2C bsg handlers
A local attacker with access to SCSI bsg handlers can leak stale kernel heap memory to device flash via uninitialized DMA buffers in the qla2xxx driver.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Local or same network only
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2026-89865?
CVE-2026-89865 is a vulnerability in Linux, published on 16 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Official 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.
Which versions are affected by CVE-2026-89865?
How do I fix CVE-2026-89865?
Apply the vendor's patch.
Is CVE-2026-89865 being exploited?
There is no known exploitation of CVE-2026-89865 in the wild and no public exploit code.
Sources
Also known as AZL-101418, BELL-CVE-2026-89865, DEBIAN-CVE-2026-89865, GHSA-rqfh-jqm9-82qm, UBUNTU-CVE-2026-89865.