ALSA: aloop: Check card index validity at probe
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 597603d615d2b19a9e451d8cfac24372856a522d · < efbc2e9e43a1b5c6d75ae47439c06896bb142ae6| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
ALSA: aloop: Check card index validity at probe
aloop driver blindly trusts that the given devptr->id value is within the proper card index range at probe. It's OK for the devices the driver itself creates at the module probe time, but if the device is bound manually via sysfs interface, this could be -1 as "none", and this leads to OOB access for index[] and other parameters.
Add a sanity check for the card index and warn/correct it if it's a value out of the range.
From the CVE record · Linux
The Linux kernel’s ALSA aloop driver does not validate a card index when a device is bound manually through sysfs. An out-of-range value can cause out-of-bounds access to index[] and other parameters. The described trigger requires local interaction with sysfs; the input does not specify authentication requirements.
Engineers running Linux kernels with the ALSA aloop driver should check whether their kernel is affected; no affected versions are specified.