ALSA: fireworks: bound device-supplied status before string array lookup
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ bde8a8f23bbe6db51fa4e81644273af18fef3d7a · < 67cfd14074cdafab5de3f7cfc0952c1a9b653e5d| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
ALSA: fireworks: bound device-supplied status before string array lookup
The status field in an EFW response is a 32-bit value supplied by the firewire device. efr_status_names[] has 17 entries so a status value outside that range goes off into the weeds when looking at the %s value.
Even worse, the status could return EFR_STATUS_INCOMPLETE which is 0x80000000, and is obviously not in that array of potential strings.
Fix this up by properly bounding the index against the array size and printing "unknown" if it's not recognized.
From the CVE record · Linux
The ALSA fireworks driver uses a status value supplied by a FireWire device to look up a string without checking that it is within the array’s bounds. A device that returns an out-of-range status can trigger an out-of-bounds lookup; the input does not specify authentication or user-interaction requirements.
Engineers running Linux kernels with the ALSA fireworks driver should check whether their kernel includes the fix; affected versions are not specified.