CVE-2026-89865

Unknown

Last modified

CVE-2026-89865 is a vulnerability of currently unknown severity. 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.

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 Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= 697a4bc69159c3396035b0506ffa55c4b2d0b1f4, < a476377a66897549dd49bee319f4df66623417b7; >= 697a4bc69159c3396035b0506ffa55c4b2d0b1f4, < 09703bc7c0be3a7a155b0ff5f21f6765ba3f519c; >= 697a4bc69159c3396035b0506ffa55c4b2d0b1f4, < 97c45c75f5cdec96b1a4fba8b1d55d0dd01af1e8; >= 697a4bc69159c3396035b0506ffa55c4b2d0b1f4, < 84bde5ce4038d9ad811e5c994305bbfcbd7a9f79; >= 697a4bc69159c3396035b0506ffa55c4b2d0b1f4, < 581590f560b74399151b3cbc88574424c2f3d2dc; >= 697a4bc69159c3396035b0506ffa55c4b2d0b1f4, < b157256c28086c434afd70cc78bf9b4d8caf1276; >= 697a4bc69159c3396035b0506ffa55c4b2d0b1f4, < a5501c42256235523c4dddf799f032dfbf4f4c77; >= 697a4bc69159c3396035b0506ffa55c4b2d0b1f4, < b47d4a1547d9ef21b2e9d1a739fe2204d4be05dc
LinuxLinux3.2

References

Timeline

Published
Last Modified
Status
Received

Frequently Asked Questions

What is CVE-2026-89865?
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.
How severe is CVE-2026-89865?
Severity scoring for CVE-2026-89865 is pending analysis.
How do I fix CVE-2026-89865?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

Are you affected by CVE-2026-89865?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST