wifi: libipw: fix key index receive bound checks
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ b453872c35cfcbdbf5a794737817f7d4e7b1b579 · < c54b643e9a0936d038921c547736574fd7382cea| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
wifi: libipw: fix key index receive bound checks
libipw_rx() reads skb->data[hdrlen + 3] to extract the WEP key index in both the software-decrypt key selection path and the hardware-decrypted IV/ICV strip path. In both places the existing guard only checks skb->len >= hdrlen + 3, which proves bytes up to hdrlen + 2 but not the byte at hdrlen + 3.
Require hdrlen + 4 bytes before reading that item in both paths. This is a local source-boundary check only; it does not change the key index semantics.
From the CVE record · Linux
The Linux kernel's libipw receive function can read beyond packet data when extracting a WEP key index from a packet that is too short. This affects both the software-decrypt key selection path and the hardware-decrypted IV/ICV strip path. The input does not specify authentication or user-interaction requirements.
Teams running Linux kernels that include libipw should check whether their kernel contains the vulnerable bounds checks; affected versions are not specified.