CVE-2026-89843

Description

In the Linux kernel, the following vulnerability has been resolved: scsi: qla2xxx: Zero-init bsg stack buffers to avoid info leak Several bsg handlers stage their request/reply in an uninitialized 256-byte on-stack buffer (uint8_t bsg[DMA_POOL_SIZE]) and fill it via sg_copy_to_buffer(), which only copies as many bytes as the user-supplied request payload. When the request is shorter than the structure, the remainder of the buffer is left holding stale stack data. qla2x00_read_fru_status() and qla2x00_read_i2c() then copy the full structure back to the reply payload with sg_copy_from_buffer(), leaking the uninitialized stack bytes to user space. The write/update paths do not copy the buffer back, but can feed uninitialized fields to the device. Zero the stack buffer at declaration in all five handlers, mirroring the heap kzalloc() approach, so short requests can no longer expose stale memory.

Is your site exposed to CVE-2026-89843?

Run a free security scan — no signup, results in seconds.

EPSS — Exploit Prediction

0.0021

Probability of exploitation

0.11%

Percentile rank

EPSS estimates the probability that this vulnerability will be exploited in the wild within the next 30 days. A higher score means more likely to be exploited.

References

Other References

https://git.kernel.org/stable/c/1c820d0900e4aacd5020b989159f6b4b2f7d0d6a https://git.kernel.org/stable/c/26bc6a2c235a70bfc9b6de412600208aca820e20 https://git.kernel.org/stable/c/4fe5790674097897a1af1367d1e384f7e5a62fb7 https://git.kernel.org/stable/c/5ab32dff910291b5e6bf6223f8a4003536c1800a https://git.kernel.org/stable/c/708c0ec1e09c52fee24b74ce9398bf3f8d1c83fd https://git.kernel.org/stable/c/7881faf862ee301ecfe3adc0725bd2fa0021cd95 https://git.kernel.org/stable/c/947c6bfcf7f5ec924995bec43e3108b98c75b44e https://git.kernel.org/stable/c/b93d3bb3afe1b44489927de1eb4e66e8536a5935

Frequently Asked Questions

What is CVE-2026-89843? +

In the Linux kernel, the following vulnerability has been resolved: scsi: qla2xxx: Zero-init bsg stack buffers to avoid info leak Several bsg handlers stage their request/reply in an uninitialized 256-byte on-stack buffer (uint8_t bsg[DMA_POOL_SIZE]) and fill it via sg_copy_to_buffer(), which only copies as many bytes as the user-supplied request payload. When the request is shorter than the structure, the remainder of the buffer is left holding stale stack data. qla2x00_read_fru_status() and qla2x00_read_i2c() then copy the full structure back to the reply payload with sg_copy_from_buffer(), leaking the uninitialized stack bytes to user space. The write/update paths do not copy the buffer back, but can feed uninitialized fields to the device. Zero the stack buffer at declaration in all five handlers, mirroring the heap kzalloc() approach, so short requests can no longer expose stale memory.

How do I check if I'm vulnerable to CVE-2026-89843? +

You can use Secably's free Website Scanner to check your website for known vulnerabilities. For infrastructure scanning, use the Port Scanner to identify exposed services that may be affected. Check the vendor advisories linked above for specific patch and version information.