ASoC: SOF: ipc4-topology: Harden loops for looking up ALH copiers
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
ASoC: SOF: ipc4-topology: Harden loops for looking up ALH copiers
Other, non DAI copier widgets could have the same stream name (sname) as the ALH copier and in that case the copier->data is NULL, no alh_data is attached, which could lead to NULL pointer dereference. We could check for this NULL pointer in sof_ipc4_prepare_copier_module() and avoid the crash, but a similar loop in sof_ipc4_widget_setup_comp_dai() will miscalculate the ALH device count, causing broken audio.
The correct fix is to harden the matching logic by making sure that the 1. widget is a DAI widget - so dai = w->private is valid 2. the dai (and thus the copier) is ALH copier
From the CVE record · Linux
The Linux kernel’s ASoC SOF IPC4 topology code can mistake a non-DAI copier widget for an ALH copier when they share a stream name. This can cause a NULL pointer dereference and crash; a related lookup can miscount ALH devices and break audio. The input does not establish an attack route, authentication requirement, or user-interaction requirement.
Engineers running the Linux kernel should check whether their build includes the affected ASoC SOF IPC4 topology code; affected versions were not provided.