scsi: qla2xxx: Zero SFP DMA buffer in FRU/I2C bsg handlers
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 697a4bc69159c3396035b0506ffa55c4b2d0b1f4 · < b157256c28086c434afd70cc78bf9b4d8caf1276| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel’s qla2xxx FRU/I2C bsg handlers use a DMA buffer without clearing it. A user-controlled payload can increase the transfer length beyond the initialized data, causing the device to read stale DMA-pool memory and write it to device flash. The input does not specify authentication or network requirements.
Engineers running Linux kernels with the qla2xxx driver should check their kernel versions against the vendor advisory; affected versions are not specified.