Strix
64.1K

CVE-2026-89843

Unknown

Last modified

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

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.

Affected Software

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

VendorProductVersions
LinuxLinux>= 697a4bc69159c3396035b0506ffa55c4b2d0b1f4, < 1c820d0900e4aacd5020b989159f6b4b2f7d0d6a; >= 697a4bc69159c3396035b0506ffa55c4b2d0b1f4, < 26bc6a2c235a70bfc9b6de412600208aca820e20; >= 697a4bc69159c3396035b0506ffa55c4b2d0b1f4, < 5ab32dff910291b5e6bf6223f8a4003536c1800a; >= 697a4bc69159c3396035b0506ffa55c4b2d0b1f4, < 947c6bfcf7f5ec924995bec43e3108b98c75b44e; >= 697a4bc69159c3396035b0506ffa55c4b2d0b1f4, < 708c0ec1e09c52fee24b74ce9398bf3f8d1c83fd; >= 697a4bc69159c3396035b0506ffa55c4b2d0b1f4, < 4fe5790674097897a1af1367d1e384f7e5a62fb7; >= 697a4bc69159c3396035b0506ffa55c4b2d0b1f4, < 7881faf862ee301ecfe3adc0725bd2fa0021cd95; >= 697a4bc69159c3396035b0506ffa55c4b2d0b1f4, < b93d3bb3afe1b44489927de1eb4e66e8536a5935
LinuxLinux3.2

References

Timeline

Published
Last Modified
Status
Received

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 severe is CVE-2026-89843?
Severity scoring for CVE-2026-89843 is pending analysis.
How do I fix CVE-2026-89843?
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

View all 2026CVEs →

Are you affected by CVE-2026-89843?

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

Scan your code now

Source: NVD / NIST