scsi: qla2xxx: Use memset_io() to clear QLAFX00 request ring slot
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 8ae6d9c7eb1004bc134813287010d57a863ba13b · < 6ee6dfd922fafd508f6bde16de30dd2db796b7a7| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
scsi: qla2xxx: Use memset_io() to clear QLAFX00 request ring slot
For QLAFX00 the request ring is ioremapped device I/O memory (ha->iobase + req_que_off), not DMA-coherent RAM, which is why the rest of the FX00 path accesses it through memcpy_toio() and the wrt_reg_* helpers. __qla2x00_alloc_iocbs() however zeroed the producer slot with a plain memset(). On architectures such as ARM64 a regular memset() may emit unaligned or block-zeroing instructions (e.g. DC ZVA) that are invalid on Device memory, leading to a synchronous external abort.
Use memset_io() to clear the slot for QLAFX00, matching the I/O accessors used elsewhere on this ring. Other adapters keep the plain memset() on their DMA-coherent rings. The zero-fill is retained for FX00 because its IOCB builders (e.g. qlafx00_fxdisc_iocb()) copy only part of the entry and rely on the unused tail being pre-zeroed.
From the CVE record · Linux
The Linux kernel qla2xxx driver clears a QLAFX00 request-ring slot with a regular memset() even though the ring is device I/O memory. On architectures such as ARM64, this can cause a synchronous external abort when the slot is cleared. The input does not specify an attack path, authentication requirements, or user interaction.
Engineers running Linux kernels with QLAFX00 adapters should check their systems; affected versions are not specified.