scsi: qla2xxx: Zero SFP DMA buffer in FRU/I2C bsg handlers
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.10.270, 5.15.221, 6.1.188, 6.6.157, 6.12.110, and 2 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 697a4bc69159c3396035b0506ffa55c4b2d0b1f4 · fixed in a476377a66897549dd49bee319f4df66623417b7; From 697a4bc69159c3396035b0506ffa55c4b2d0b1f4 · fixed in 09703bc7c0be3a7a155b0ff5f21f6765ba3f519c; From 697a4bc69159c3396035b0506ffa55c4b2d0b1f4 · fixed in 97c45c75f5cdec96b1a4fba8b1d55d0dd01af1e8; From 697a4bc69159c3396035b0506ffa55c4b2d0b1f4 · fixed in 84bde5ce4038d9ad811e5c994305bbfcbd7a9f79; From 697a4bc69159c3396035b0506ffa55c4b2d0b1f4 · fixed in 581590f560b74399151b3cbc88574424c2f3d2dc; From 697a4bc69159c3396035b0506ffa55c4b2d0b1f4 · fixed in b157256c28086c434afd70cc78bf9b4d8caf1276; From 697a4bc69159c3396035b0506ffa55c4b2d0b1f4 · fixed in a5501c42256235523c4dddf799f032dfbf4f4c77; From 697a4bc69159c3396035b0506ffa55c4b2d0b1f4 · fixed in b47d4a1547d9ef21b2e9d1a739fe2204d4be05dc
- Linux Linux
3.2
- KernelLinux
From 3.2.0 · fixed in 5.10.270; From 5.11.0 · fixed in 5.15.221; From 5.16.0 · fixed in 6.1.188; From 6.2.0 · fixed in 6.6.157; From 6.7.0 · fixed in 6.12.110; From 6.13.0 · fixed in 6.18.51; From 6.19.0 · fixed in 7.2.5
References 8
git.kernel.org
- stable/c/a476377a66897549dd49bee319f4df66623417b7
- stable/c/09703bc7c0be3a7a155b0ff5f21f6765ba3f519c
- stable/c/97c45c75f5cdec96b1a4fba8b1d55d0dd01af1e8
- stable/c/84bde5ce4038d9ad811e5c994305bbfcbd7a9f79
- stable/c/581590f560b74399151b3cbc88574424c2f3d2dc
- stable/c/b157256c28086c434afd70cc78bf9b4d8caf1276
- stable/c/a5501c42256235523c4dddf799f032dfbf4f4c77
- stable/c/b47d4a1547d9ef21b2e9d1a739fe2204d4be05dc