ALSA: control: Validate buf_len before strnlen() in snd_ctl_elem_init_enum_names()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 8d448162bda5ae3b5ecb26fe50c8fbbeae99faa4 · < 654c818a69c21d2bea4e8fd9eae7da865df9a5c8| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
ALSA: control: Validate buf_len before strnlen() in snd_ctl_elem_init_enum_names()
snd_ctl_elem_init_enum_names() advances pointer p through the names buffer while decrementing buf_len. If buf_len reaches zero but items remain, the next iteration calls strnlen(p, 0).
While strnlen(p, 0) returns 0 and would hit the existing name_len == 0 error path, CONFIG_FORTIFY_SOURCE's fortified strnlen() first checks maxlen against __builtin_dynamic_object_size(). When Clang loses track of p's object size inside the loop, this triggers a BRK exception panic before the return value is examined.
Add a buf_len == 0 guard at the loop entry to prevent calling fortified strnlen() on an exhausted buffer.
Found by kernel fuzz testing through Xiaomi Smartphone.
From the CVE record · Linux
The Linux kernel’s ALSA control code can call fortified strnlen() after a names buffer is exhausted. With CONFIG_FORTIFY_SOURCE enabled and Clang unable to determine the pointer’s object size, this can trigger a kernel panic. The input does not specify whether exploitation requires network access, authentication, or user interaction.
Engineers running Linux kernels with ALSA control should check their affected versions; no version range was provided.