dmaengine: zynqmp_dma: In struct zynqmp_dma_chan fix desc_size data type
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ b0cc417c1637192be658e68a74c8d1568e3d35f6 · < f9a9f43a62a04ec3183fb0da9226c7706eed0115| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
dmaengine: zynqmp_dma: In struct zynqmp_dma_chan fix desc_size data type
In zynqmp_dma_alloc/free_chan_resources functions there is a potential overflow in the below expressions.
dma_alloc_coherent(chan->dev, (2 * chan->desc_size * ZYNQMP_DMA_NUM_DESCS), &chan->desc_pool_p, GFP_KERNEL);
dma_free_coherent(chan->dev,(2 * ZYNQMP_DMA_DESC_SIZE(chan) * ZYNQMP_DMA_NUM_DESCS), chan->desc_pool_v, chan->desc_pool_p);
The arguments desc_size and ZYNQMP_DMA_NUM_DESCS were 32 bit. Though this overflow condition is not observed but it is a potential problem in the case of 32-bit multiplication. Hence fix it by changing the desc_size data type to size_t.
In addition to coverity fix it also reuse ZYNQMP_DMA_DESC_SIZE macro in dma_alloc_coherent API argument.
Addresses-Coverity: Event overflow_before_widen.
From the CVE record · Linux
The Linux kernel’s zynqmp_dma driver has a potential 32-bit multiplication overflow when allocating or freeing DMA descriptor resources. The overflow was not observed, and the input does not establish how an attacker could trigger or exploit it or whether authentication or user interaction is required.
Engineers running the Linux kernel with the zynqmp_dma driver should check their deployments; affected versions are not specified.