scsi: qla2xxx: Use memset_io() to clear QLAFX00 request ring slot
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel e41d28d9a242c4005b7d01a7ee7769405a6a2c2e, Kernel 0eca1d7a4dac793224e6e295e29e00245e96cf16, Kernel 2df8c8630904794100189fa3d70598642e1877ce and 12 more.
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.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | >=8ae6d9c7eb1004bc134813287010d57a863ba13b <e41d28d9a242c4005b7d01a7ee7769405a6a2c2e, >=8ae6d9c7eb1004bc134813287010d57a863ba13b <0eca1d7a4dac793224e6e295e29e00245e96cf16, >=8ae6d9c7eb1004bc134813287010d57a863ba13b <2df8c8630904794100189fa3d70598642e1877ce, >=8ae6d9c7eb1004bc134813287010d57a863ba13b <337026cf8149dcfedacd60d6d7081bff10ee5cd4, >=8ae6d9c7eb1004bc134813287010d57a863ba13b <53eb96c244d150dfb8cc4b5b0492ab53755f3701, >=8ae6d9c7eb1004bc134813287010d57a863ba13b <626e44f3d8a924a97a3848a9fd45833947e081e9, >=8ae6d9c7eb1004bc134813287010d57a863ba13b <6e8f1144d06cfd8cf8c346066efd8f572b28f768, >=8ae6d9c7eb1004bc134813287010d57a863ba13b <6ee6dfd922fafd508f6bde16de30dd2db796b7a7, =3.10 | e41d28d9a242c4005b7d01a7ee7769405a6a2c2e, 0eca1d7a4dac793224e6e295e29e00245e96cf16, 2df8c8630904794100189fa3d70598642e1877ce, 337026cf8149dcfedacd60d6d7081bff10ee5cd4, 53eb96c244d150dfb8cc4b5b0492ab53755f3701, 626e44f3d8a924a97a3848a9fd45833947e081e9, 6e8f1144d06cfd8cf8c346066efd8f572b28f768, 6ee6dfd922fafd508f6bde16de30dd2db796b7a7 |
| linux-kernel: Kernel | >=5.11.0 <5.15.224, >=5.16.0 <6.1.191, >=6.13.0 <6.18.53, >=6.19.0 <7.2.7, >=6.2.0 <6.6.160, >=6.7.0 <6.12.112, >=3.10.0 <5.10.273 | 5.15.224, 6.1.191, 6.18.53, 7.2.7, 6.6.160, 6.12.112, 5.10.273 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket