HIGH Introduced in 2.6.32
cfg80211 AssocResp OOB
CVE-2026-93806
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
KernelScan AI7.8HIGH
01Description
In the Linux kernel, the following vulnerability has been resolved: wifi: cfg80211: validate assoc response length before status and IE access cfg80211_rx_assoc_resp() initialises the status and response-IE fields of cfg80211_connect_resp_params from the management frame before proving that the frame is long enough for those offsets. S1G and regular association responses also have different IE offsets, but the S1G path only patched resp_ie after the unsafe initialiser had already run. Defer resp_ie, resp_ie_len, and status to after the link-iteration loop. Use a bool to remember whether the frame is S1G, then validate the appropriate minimum length and set all three fields in a single if/else block. Funnel short-frame and SME-reject cleanup through a shared free_bss label for the abandon paths.
02KernelScan AI Analysis
Risk summary
Any device with WiFi enabled is at risk from a nearby attacker—such as a rogue access point or wireless man-in-the-middle—who sends a too-short association response frame. The bug causes an out-of-bounds read that can leak kernel memory and crash the system. No privileges on the target device are required; only radio proximity during WiFi association.
Vulnerability analysis
When a WiFi device receives an association response frame, the wireless configuration layer extracts the status code and information-element fields from the frame before verifying the frame is long enough to contain them. A too-short frame causes the information-element length calculation to wrap to a huge value, making the kernel read far past the frame buffer—which can leak kernel memory and crash the system when the over-read hits an unmapped page. The fix defers all field extraction until after a length check that accounts for the different offsets used by sub-1 GHz and regular association responses, and cleanly abandons the connection if the frame is too short. The flaw is reachable by any nearby radio that can send WiFi management frames to a device during association, such as a rogue access point or a man-in-the-middle, and requires no account or privileges on the target.
Lifecycle
03Fix Versions
| Branch | Introduced | Fixed in | Patch commit |
|---|---|---|---|
| 6.1 | 2.6.32 | 6.1.189 | 3bcaaaa4ad33 |
| 6.12 | 2.6.32 | 6.12.111 | a57310600c1e |
| 6.18 | 2.6.32 | 6.18.53 | 78ac450ad462 |
| 6.6 | 2.6.32 | 6.6.158 | 71be658246c9 |
| mainline | 2.6.32 | 7.2 | b760113aeca2 |
| cip/6.1 | 2.6.32 | 6.1.189-cip61 | 3bcaaaa4ad33 |
| cip/6.1-rt | 2.6.32 | 6.1.189-cip61-rt32 | 3bcaaaa4ad33 |
| cip/6.12 | 2.6.32 | 6.12.111-cip32 | a57310600c1e |
04CIP Kernels
State of the newest release of each Civil Infrastructure Platform SLTS tree, from CIP's own fix records.
| CIP tree | State |
|---|---|
| cip/6.12 | Fixed in 6.12.111-cip32 |
| cip/6.1 | Fixed in 6.1.189-cip61 |
| cip/6.1-rt | Fixed in 6.1.189-cip61-rt32 |
| cip/5.10 | Affected — no CIP fix yet (latest 5.10.271-cip78) |
| cip/5.10-rt | Affected — no CIP fix yet (latest 5.10.268-cip77-rt34) |
| cip/4.19 | Affected — no CIP fix yet (latest 4.19.325-cip136) |
| cip/4.19-rt | Affected — no CIP fix yet (latest 4.19.325-cip136-rt50) |
| cip/4.4 | Affected — no CIP fix yet (latest 4.4.302-cip115) |
| cip/4.4-rt | Affected — no CIP fix yet (latest 4.4.302-cip115-rt63) |