wifi: mac80211: validate extension-frame layout before RX
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
wifi: mac80211: validate extension-frame layout before RX
Extension frames only have the extension header at the regular 802.11 header offset. The generic RX path can still reach helpers and interface dispatch code that read regular header address fields before unsupported extension subtypes are dropped.
mac80211 currently only handles S1G beacon extension frames. Drop other extension subtypes before they can reach regular-header RX processing. For S1G beacons, linearize the SKB with the management-frame path and require the fixed S1G beacon header, including optional fixed fields indicated by frame control, before generic RX dispatch.
Route S1G beacons through the station/default-link RX path without regular-header station lookup. Avoid regular-header address reads in the mac80211 RX paths that process S1G extension beacons, including accept-frame, duplicate-detection, address-copy, and MLO address-translation paths.
Also make ieee80211_get_bssid() length-safe before returning the S1G source-address pointer.
From the CVE record · Linux
The Linux kernel’s mac80211 receive path can read regular 802.11 header fields from extension frames that do not have those fields. A sender of extension frames received over Wi-Fi could trigger these invalid reads before unsupported frames are dropped. The input does not specify authentication or user-interaction requirements.
Engineers running Linux systems that use the mac80211 Wi-Fi stack should check their kernel versions against the vendor advisory; affected versions are not listed.