wifi: b43legacy: enforce bounds check on firmware key index in RX path
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 75388acd0cd827dc1498043daa7d1c760902cd67 · < 9d1bc155802943e92c57a5fb923d23edfbf0b525| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
wifi: b43legacy: enforce bounds check on firmware key index in RX path
Same fix as b43: the firmware-controlled key index in b43legacy_rx() can exceed dev->max_nr_keys. The existing B43legacy_WARN_ON is non-enforcing in production builds, allowing an out-of-bounds read of dev->key[].
Make the check enforcing by dropping the frame for invalid indices.
From the CVE record · Linux
The Linux kernel's b43legacy RX path does not enforce bounds on a firmware-controlled key index in production builds. When that index exceeds the key limit, processing a frame can read beyond the key array; the input does not specify attacker access or user-interaction requirements.
Engineers running Linux kernels with the b43legacy Wi-Fi driver should check their kernel version; affected versions are not specified.