ASoC: stm32: spdifrx: fix dma channel release in stm32_spdifrx_remove
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 794df9448edb55978e50372f083aeedade1b2844 · < 9bb4af400c386374ab1047df44c508512c08c31f| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
ASoC: stm32: spdifrx: fix dma channel release in stm32_spdifrx_remove
In case of error when requesting ctrl_chan DMA channel, ctrl_chan is not null. So the release of the dma channel leads to the following issue: [ 4.879000] st,stm32-spdifrx 500d0000.audio-controller: dma_request_slave_channel error -19 [ 4.888975] Unable to handle kernel NULL pointer dereference at virtual address 000000000000003d [...] [ 5.096577] Call trace: [ 5.099099] dma_release_channel+0x24/0x100 [ 5.103235] stm32_spdifrx_remove+0x24/0x60 [snd_soc_stm32_spdifrx] [ 5.109494] stm32_spdifrx_probe+0x320/0x4c4 [snd_soc_stm32_spdifrx]
To avoid this issue, release channel only if the pointer is valid.
From the CVE record · Linux
The STM32 SPDIFRX driver can dereference a null pointer while releasing a DMA channel after a channel request fails. This can crash the kernel; the input does not describe an attacker path, authentication requirement, or user interaction.
Engineers running Linux kernels with the STM32 SPDIFRX driver should check their deployments; affected versions are not specified.