CVE-2026-89865

CVE CVE-2026-89865EUVD EUVD-2026-80465Published 2026-09-16T10:31:35.000Z

What the advisory describes

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.

Source: EUVD (ENISA), in the words of the advisory.

Products the advisory names

These come from the advisory itself, not from any check we performed.

Linux — Linux 697a4bc69159c3396035b0506ffa55c4b2d0b1f4 <97c45c75f5cdec96b1a4fba8b1d55d0dd01af1e8; 697a4bc69159c3396035b0506ffa55c4b2d0b1f4 <581590f560b74399151b3cbc88574424c2f3d2dc; patch: 6.18.51; patch: 6.12.110; patch: 0; 3.2; patch: 6.1.188; 697a4bc69159c3396035b0506ffa55c4b2d0b1f4 <a476377a66897549dd49bee319f4df66623417b7; 697a4bc69159c3396035b0506ffa55c4b2d0b1f4 <84bde5ce4038d9ad811e5c994305bbfcbd7a9f79; 697a4bc69159c3396035b0506ffa55c4b2d0b1f4 <b47d4a1547d9ef21b2e9d1a739fe2204d4be05dc; 697a4bc69159c3396035b0506ffa55c4b2d0b1f4 <09703bc7c0be3a7a155b0ff5f21f6765ba3f519c; patch: 6.6.157; 697a4bc69159c3396035b0506ffa55c4b2d0b1f4 <b157256c28086c434afd70cc78bf9b4d8caf1276; patch: 5.10.270; patch: 5.15.221; patch: 7.2.5; 697a4bc69159c3396035b0506ffa55c4b2d0b1f4 <a5501c42256235523c4dddf799f032dfbf4f4c77; patch: 7.3-rc1

The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.

Carried in the product catalogue

An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.

Linux — Linux

Does this concern one of your customers?

This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.

Try it for 28 days

Patchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.