netdev - [Regression] Bug 216711 - null SSID reported by systemd-networkd when connected to a WPA3 network

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <fa0d345a-c3e5-fbf2-4fab-e43235e779b6@leemhuis.info>
Date:   Mon, 21 Nov 2022 09:32:56 +0100
From:   Thorsten Leemhuis <regressions@...mhuis.info>
To:     Johannes Berg <johannes.berg@...el.com>
Cc:     Zoddo <kernel+bugzilla@...do.fr>,
        "linux-wireless@...r.kernel.org" <linux-wireless@...r.kernel.org>,
        netdev <netdev@...r.kernel.org>
Subject: [Regression] Bug 216711 - null SSID reported by systemd-networkd when
 connected to a WPA3 network

Hi, this is your Linux kernel regression tracker speaking.

I noticed a regression report in bugzilla.kernel.org. As many (most?)
kernel developer don't keep an eye on it, I decided to forward it by
mail. Quoting from https://bugzilla.kernel.org/show_bug.cgi?id=216711 :

>  Zoddo 2022-11-19 15:36:02 UTC
> 
> Created attachment 303236 [details]
> Bisect log
> 
> Starting with linux 5.19.2, systemd-networkd reports a "(null)" SSID when connected to WPA3 network.
> 
> Steps to reproduce:
> 1. Get a system with systemd-networkd (maybe this issue can be exhibited with other methods, but using systemd-netword is the only one I know; I haven't found how to get this data directly from the kernel)
> 2. Connect to a wireless network using WPA3.
> 3. Run "networkctl status <wlan interface>", and observe that "WiFi access point" shows "(null)" instead of the network's SSID.
> 4. If you try again with a WPA2 network, the SSID is shown as expected. WPA3 network also behaves as expected on kernel <=5.19.1
> 
> This bug also affects linux 6.0 (tested on 6.0.8).
> 
> 
> Bisection identified the following commit as the culprit:
> (full bisect log attached)
> 
> 7a53ad13c09150076b7ddde96c2dfc5622c90b45 is the first bad commit
> commit 7a53ad13c09150076b7ddde96c2dfc5622c90b45
> Author: Johannes Berg <johannes.berg@...el.com>
> Date:   Thu Apr 14 16:50:57 2022 +0200
> 
>     wifi: cfg80211: do some rework towards MLO link APIs
>     
>     [ Upstream commit 7b0a0e3c3a88260b6fcb017e49f198463aa62ed1 ]
>     
>     In order to support multi-link operation with multiple links,
>     start adding some APIs. The notable addition here is to have
>     the link ID in a new nl80211 attribute, that will be used to
>     differentiate the links in many nl80211 operations.


See the ticket for more details.

BTW, let me use this mail to also add the report to the list of tracked
regressions to ensure it's doesn't fall through the cracks:

#regzbot introduced: 7b0a0e3c3a882
https://bugzilla.kernel.org/show_bug.cgi?id=216711
#regzbot ignore-activity

Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)

P.S.: As the Linux kernel's regression tracker I deal with a lot of
reports and sometimes miss something important when writing mails like
this. If that's the case here, don't hesitate to tell me in a public
reply, it's in everyone's interest to set the public record straight.