The definitive selling point of the IEEE 802.11be (Wi-Fi 7) standard is Multi-Link Operation (MLO). Unlike legacy dual-band routers that force client devices to associate with either the 2.4GHz, 5GHz, or 6GHz spectrum independently, MLO aggregates multiple physical channels simultaneously. Devices transmit and receive packets concurrently across 5GHz and 6GHz to achieve sub-millisecond deterministic latency and 30+ Gbps throughput.

However, an international team of wireless security researchers has published details on a critical architectural flaw tracked as CVE-2026-28192 (MLO-Desync). This vulnerability permits nearby attackers to intercept, desynchronize, and inject malicious control frames across uncoordinated multi-link sessions. Here is the technical mechanics of the exploit and how to secure your network.

In standard Wi-Fi 7 MLO, client devices establish a single logical MAC interface that maps across multiple physical Affiliated MAC (AP-MLD) links. When operating in STR (Simultaneous Transmit and Receive) mode, the device communicates over a high-bandwidth 6GHz primary link while maintaining a low-power 5GHz secondary link for ACK confirmations and retransmissions.

The flaw resides in how the 802.11be specification handles Cross-Link Channel Switch Announcements (CSA) and Link Teardown handshakes:

  1. Rogue Beacon Injection: An attacker within physical range deploys a rogue software-defined radio (SDR) broadcasting forged 802.11be management frames on the 5GHz frequency band, matching your router's BSSID.
  2. State Desynchronization: Because many consumer routers only enforce Protected Management Frames (PMF) strictly on the 6GHz band while allowing relaxed PMF negotiation on legacy 5GHz channels for backward compatibility, the client accepts the rogue CSA packet on 5GHz.
  3. Traffic Redirection: The client mistakenly tears down its encrypted 6GHz link and falls back to an unencrypted or downgrade-vulnerable 5GHz link managed by the rogue access point, opening the door to session hijacking and credential interception.
Router Vendor Affected Hardware Series Patch Version Mitigation Status
ASUS ROG Rapture GT-BE98, ZenWiFi BQ16 Firmware 3.0.0.6.102_4120+ ✅ Patch Released
TP-Link Archer BE800/BE900, Deco BE85 Firmware v1.3.4 Build 20260915+ ✅ Patch Released
Netgear Nighthawk RS700S, Orbi RBE970 Firmware V1.1.8.44_1.0.82+ ⚠️ Rolling Beta Update
Ubiquiti UniFi UniFi U7 Pro, U7 Pro Max UniFi AP Firmware 7.1.38+ ✅ Patch Released

2. Step-by-Step Router Hardening: Eliminating MLO Desync

Until your router manufacturer issues an automatic Over-The-Air (OTA) firmware upgrade, you should immediately apply the following three security configurations within your router's admin console:

🚀
Interactive Tool

RAM Speed & True Latency Calculator

Calculate exact real response times in nanoseconds (ns) and dual-channel bandwidth for AMD Ryzen & Intel PC builds.

Calculate Latency →

Step A: Force Protected Management Frames (PMF) to "Required"

By default, many Wi-Fi 7 routers set PMF to "Capable" (optional) on 2.4GHz and 5GHz to support older IoT smart-home appliances. This allows attackers to forge unauthenticated deauthentication frames. Change PMF to Required (Mandatory) across all radio bands:

Router Admin → Wireless Settings → Advanced Security:
├── Security Mode: WPA3-Personal (WPA3-SAE) or WPA3-Enterprise
└── Protected Management Frames (802.11w): REQUIRED (Do NOT select Optional/Capable)

Step B: Restrict MLO Link Aggregation to 5GHz + 6GHz Only

Never allow your MLO multi-link profile to include the 2.4GHz spectrum. The 2.4GHz band is saturated with high background noise, lacks robust hardware cryptographic protection on older controllers, and serves as the primary vector for rogue packet injection. Configure MLO to pair 5GHz Channel 149-165 + 6GHz Channel 37-69 exclusively.

Step C: Segregate Legacy 2.4GHz IoT Hardware into a Dedicated VLAN

If you have smart bulbs, security cameras, or robotic vacuums that cannot connect to WPA3-Mandatory networks, create an isolated Guest Network or IoT VLAN locked to 2.4GHz WPA2-Personal. Ensure AP Isolation is toggled ON to prevent compromised smart-plugs from surveying your high-speed Wi-Fi 7 workstation traffic.

3. Operating System Client Mitigations

Client operating systems require driver-level patches to reject uncoordinated multi-link teardowns. Ensure your client machines are running the latest network stacks:

  • Windows 11: Install Cumulative Update KB5124010 or newer. Verify that your Intel BE200 or Qualcomm FastConnect 7800 driver is version 23.60.0.4 or higher via Device Manager.
  • Linux: Update to kernel 6.12+ and verify that wpa_supplicant is compiled with CONFIG_IEEE80211BE=y and CONFIG_PMF=y in /etc/wpa_supplicant.conf.
  • Android 17 / iOS 20: Both mobile operating systems already enforce mandatory PMF validation on all affiliated links during MLO handshakes by default.

4. Security Audit Checklist

Maintaining a secure Wi-Fi 7 environment requires ongoing hygiene. Perform an audit using Wireshark or a wireless spectrum analyzer: verify that zero unencrypted 802.11 management frames traverse your 5GHz network, and ensure your router's remote WAN management port (typically port 8443 or 8080) is permanently disabled.