#1147955 wpasupplicant: Fix SAE reporting over dbus, upstream patch available

Package:
wpasupplicant
Source:
wpasupplicant
Description:
client support for WPA and WPA2 (IEEE 802.11i)
Submitter:
ValdikSS
Date:
2026-09-19 05:43:02 UTC
Severity:
normal
Tags:
#1147955#5
Date:
2026-09-15 17:12:45 UTC
From:
To:
Dear Maintainer,

wpa_supplicant fails to report WPA3 SAE support in KeyMgmt dbus reply
under certain conditions, which affects Raspberry Pi computers (Broadcom
Wi-Fi).

NetworkManager expects SAE to be present in KeyMgmt to correctly connect
to WPA3 networks. The upstream patch fixes this issue.

Patch:

https://git.w1.fi/cgit/hostap/commit/?id=26c7f1bc107843f0ae57d35f3c9363367a0d11e7
   or if w1.fi in unreachable, which seems to be common

https://chromium.googlesource.com/external/w1.fi/cgit/hostap/+/26c7f1bc107843f0ae57d35f3c9363367a0d11e7%5E%21/#F0

The patch has been included in 2.12 release.
Please pick it for the current WPA-supplicant in Trixie and, if
possible, Bookworm.

More information:
https://github.com/raspberrypi/linux/issues/7528#issuecomment-5665763412

#1147955#10
Date:
2026-09-19 05:40:13 UTC
From:
To:
Please do not apply this patch to trixie on its own. Raspberry Pi OS shipped it on
2026-09-17 as 2:2.10-24+rpt1 and it takes a Raspberry Pi Zero 2 W (brcmfmac,
BCM43430/1) off Wi-Fi permanently on any WPA2/WPA3 transition-mode AP. Full analysis
with logs and the exact mechanism: https://github.com/raspberrypi/linux/issues/7634
Short version: brcmfmac sets NL80211_FEATURE_SAE (external SAE auth) although the
43430/1 firmware cannot complete the handshake. With the patch, wpa_supplicant reports
"sae" over D-Bus, and NetworkManager 1.52.1 (trixie) then appends SAE to key_mgmt for
every wpa-psk profile in station mode. wpa_supplicant prefers SAE over PSK, the
association fails, and there is no fallback. The NetworkManager escape hatch
(wifi-sec.pmf=disable) only works in station mode since upstream commit b00c6749
(2025-06-05), which is in 1.56+ and not in trixie's 1.52.1.
So in trixie the patch is safe only together with one of:

     *
a NetworkManager stable update carrying b00c6749, so pmf=disable opts out, or
     *
brcmfmac not advertising NL80211_FEATURE_SAE on chips where it does not work.

Affected: Debian trixie on Raspberry Pi Zero 2 W / 3B / Zero W (43430 family) with the
Debian kernel, and Raspberry Pi OS trixie. Workaround on the box: hold wpasupplicant at
2:2.10-24, or brcmfmac.feature_disable with the SAE_EXT bit for the running kernel.


Martin Werner, DK5EN