ASoC: SOF: ipc3-topology: Prevent double freeing of ipc_control_data via load_bytes
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
5.18.185.19.26.0In the Linux kernel, the following vulnerability has been resolved:
ASoC: SOF: ipc3-topology: Prevent double freeing of ipc_control_data via load_bytes
We have sanity checks for byte controls and if any of the fail the locally allocated scontrol->ipc_control_data is freed up, but not set to NULL.
On a rollback path of the error the higher level code will also try to free the scontrol->ipc_control_data which will eventually going to lead to memory corruption as double freeing memory is not a good thing.
From the CVE record · Linux
The Linux kernel's ASoC SOF ipc3-topology code can free ipc_control_data twice when a byte-control sanity check fails and the error path rolls back. This can cause memory corruption. The input does not specify how an attacker could trigger the condition or whether authentication or user interaction is required.
Engineers running Linux kernels with ASoC SOF ipc3-topology should check their kernel versions; affected versions are not specified.