ASoC: SOF: ipc3-control: Fix heap overflow in bytes_ext put/get
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 67ec2a091630c28ea8d05db2bd7178a05b04b7e6 · < fd46668d538993218eea19c6925c868ac0f2630c| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
ASoC: SOF: ipc3-control: Fix heap overflow in bytes_ext put/get
The ipc_control_data buffer is allocated as kzalloc(max_size), where max_size covers the entire struct sof_ipc_ctrl_data including its flexible array payload. However, the bounds checks in bytes_ext_put and _bytes_ext_get compared user data lengths against max_size directly, ignoring that cdata->data sits at an offset of sizeof(struct sof_ipc_ctrl_data) bytes into the allocation.
This allowed writing up to sizeof(struct sof_ipc_ctrl_data) bytes past the end of the heap buffer from unprivileged userspace via the ALSA TLV kcontrol interface, and similarly allowed over-reading adjacent heap data on the get path.
Fix all bounds checks to subtract sizeof(*cdata) from max_size so they reflect the actual space available at the cdata->data offset. Also fix the error-path restore in bytes_ext_put which wrote to cdata->data instead of cdata, causing the same overflow.
From the CVE record · Linux
The Linux kernel’s ASoC SOF ipc3-control code has incorrect bounds checks in its bytes_ext put and get paths. A local, unprivileged user can use the ALSA TLV kcontrol interface to write past a heap buffer or read adjacent heap data.
Engineers running Linux kernels with ASoC SOF ipc3-control should check their exposure; affected versions were not specified.