ASoC: dapm: Fix off-by-one check on the second enum channel
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 3727b4968453dbab8fe18f979d67285eb6b66801 · < 10a36512c21f861a03fba461a7ead09023df9c1b| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
ASoC: dapm: Fix off-by-one check on the second enum channel
The snd_soc_dapm_put_enum_double() rejects item[0] once it reaches e->items, but it lets item[1] be equal to it. Both go on to snd_soc_enum_item_to_val(), which indexes e->values with no bound of its own, so an enum with a value table reads one element past the end.
The indexing arrived with the MUX consolidation, which relaxed the item[1] check in the same hunk. The value MUX handler it deleted used >= there, and the snd_soc_put_enum_double() in soc-ops.c still does.
Only adav80x pairs a value table with two shifts, and its second channel looks accidental, but the control does report two values. Writing three into it reads off the end of adav80x_mux_values. The core catches that only under CONFIG_SND_CTL_INPUT_VALIDATION, which defaults off.
From the CVE record · Linux
The Linux kernel’s ASoC DAPM double-enum handler can read one element past an enum value table when the second channel is set to an out-of-range value. This affects the adav80x control when someone can write to it and CONFIG_SND_CTL_INPUT_VALIDATION is disabled, as it is by default.
Engineers running Linux kernels with the adav80x audio driver should check whether their kernel includes the fix; affected versions were not specified.