ALSA: usb-audio: caiaq: validate EP1 reply lengths
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 523f1dce37434a9a6623bf46e7893e2b4b10ac3c · < 74f3c639f64fa5da4e1613149798b5089bce2807| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
ALSA: usb-audio: caiaq: validate EP1 reply lengths
usb_ep1_command_reply_dispatch() uses buf[0] as a command byte and then reads command-specific fixed items from the same URB buffer. Several paths use buf + 1, buf[1], buf[2], or buf + 3 without first proving that urb->actual_length contains those bytes.
Add per-command length checks, use a payload length derived from the bytes after the command byte for the control-state copy, and reject short analog input payloads before the input helper reads fixed offsets from the EP1 reply.
From the CVE record · Linux
The ALSA caiaq USB-audio driver reads command-specific fields from EP1 replies without first checking that the reply contains enough bytes. A short reply can cause an out-of-bounds read when the kernel processes it. The input does not specify an attacker access path, authentication requirement, or user interaction.
Engineers running Linux kernels with the ALSA caiaq USB-audio driver should check their kernel version; affected versions are not specified.