CVE-2024-43841

What it actually does

virt_wifi connection code skips SSID validation from user space (only checks BSSID) and calls cfg80211_connect_result with WLAN_STATUS_SUCCESS for mismatched SSID, causing cfg80211_bss lookup failure and WARN_ON(bss_not_found).

Why it matters to the business

Triggers kernel warnings during WiFi connection attempts on systems using virt_wifi, potentially disrupting wireless networking operations across environments with 572 downstream dependents; low urgency given zero KEV status and flat EPSS.

How an attack unfolds

An attacker or automated script issues a connect request specifying an SSID different from the one advertised by virt_wifi; the driver omits the SSID check, reports success, and cfg80211 emits the warning when it cannot locate the BSS.

How to fix it

Apply the upstream fix that adds an SSID comparison in the virt_wifi connection handler before calling cfg80211_connect_result; no specific package versions listed for the kernel component.

How to confirm the fix worked

Confirm the SSID check is present in the connect routine and that mismatched SSID requests now return an appropriate failure status instead of success; test with deliberate SSID mismatch and verify absence of the warning.

Typical attack path

1. Identify a system using the virt_wifi driver
2. Issue a cfg80211 connect request with mismatched SSID via userspace tools or API
3. Observe the resulting WARN_ON(bss_not_found) in kernel logs

How to detect it

Search kernel logs and dmesg for WARN_ON(bss_not_found) originating from cfg80211 after virt_wifi connect attempts; correlate with userspace WiFi management processes issuing connect requests.

What your security team should do

• Patch affected kernels to include the SSID validation change at earliest maintenance window
• Monitor kernel logs for repeated WARN_ON(bss_not_found) entries from virt_wifi
• Limit use of virt_wifi in production until validated