scsi: qla2xxx: Zero SFP DMA buffer in FRU/I2C bsg handlers
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel b47d4a1547d9ef21b2e9d1a739fe2204d4be05dc, Kernel 09703bc7c0be3a7a155b0ff5f21f6765ba3f519c, Kernel 581590f560b74399151b3cbc88574424c2f3d2dc and 12 more.
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
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | >=697a4bc69159c3396035b0506ffa55c4b2d0b1f4 <b47d4a1547d9ef21b2e9d1a739fe2204d4be05dc, >=697a4bc69159c3396035b0506ffa55c4b2d0b1f4 <09703bc7c0be3a7a155b0ff5f21f6765ba3f519c, >=697a4bc69159c3396035b0506ffa55c4b2d0b1f4 <581590f560b74399151b3cbc88574424c2f3d2dc, >=697a4bc69159c3396035b0506ffa55c4b2d0b1f4 <84bde5ce4038d9ad811e5c994305bbfcbd7a9f79, >=697a4bc69159c3396035b0506ffa55c4b2d0b1f4 <97c45c75f5cdec96b1a4fba8b1d55d0dd01af1e8, >=697a4bc69159c3396035b0506ffa55c4b2d0b1f4 <a476377a66897549dd49bee319f4df66623417b7, >=697a4bc69159c3396035b0506ffa55c4b2d0b1f4 <a5501c42256235523c4dddf799f032dfbf4f4c77, >=697a4bc69159c3396035b0506ffa55c4b2d0b1f4 <b157256c28086c434afd70cc78bf9b4d8caf1276, =3.2 | b47d4a1547d9ef21b2e9d1a739fe2204d4be05dc, 09703bc7c0be3a7a155b0ff5f21f6765ba3f519c, 581590f560b74399151b3cbc88574424c2f3d2dc, 84bde5ce4038d9ad811e5c994305bbfcbd7a9f79, 97c45c75f5cdec96b1a4fba8b1d55d0dd01af1e8, a476377a66897549dd49bee319f4df66623417b7, a5501c42256235523c4dddf799f032dfbf4f4c77, b157256c28086c434afd70cc78bf9b4d8caf1276 |
| linux-kernel: Kernel | >=5.11.0 <5.15.221, >=5.16.0 <6.1.188, >=6.13.0 <6.18.51, >=6.19.0 <7.2.5, >=6.2.0 <6.6.157, >=6.7.0 <6.12.110, >=3.2.0 <5.10.270 | 5.15.221, 6.1.188, 6.18.51, 7.2.5, 6.6.157, 6.12.110, 5.10.270 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket