accel/qaic: Treat remaining == 0 as error in find_and_map_user_pages()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
accel/qaic: Treat remaining == 0 as error in find_and_map_user_pages()
Currently, if find_and_map_user_pages() takes a DMA xfer request from the user with a length field set to 0, or in a rare case, the host receives QAIC_TRANS_DMA_XFER_CONT from the device where resources->xferred_dma_size is equal to the requested transaction size, the function will return 0 before allocating an sgt or setting the fields of the dma_xfer struct. In that case, encode_addr_size_pairs() will try to access the sgt which will lead to a general protection fault.
Return an EINVAL in case the user provides a zero-sized ALP, or the device requests continuation after all of the bytes have been transferred.
From the CVE record · Linux
The Linux kernel’s accel/qaic driver can access an uninitialized scatter-gather table when a user submits a zero-length DMA transfer request. The same fault can occur if the device requests continuation after all requested bytes have been transferred. Either condition can trigger a general protection fault.
Engineers running Linux kernels with the accel/qaic driver should check their systems; affected versions were not specified.