From: Julien Olivain via buildroot <buildroot@buildroot.org>
To: Waldemar Brodkorb <wbx@openadk.org>
Cc: buildroot@buildroot.org, Sergey Matyukevich <geomatsi@gmail.com>
Subject: Re: [Buildroot] [PATCH] package/wpa_supplicant: security bump to 2.12
Date: Sun, 16 Aug 2026 17:49:01 +0200 [thread overview]
Message-ID: <baca04d491cacc42082435db7be33f74@free.fr> (raw)
In-Reply-To: <aoGwcjcKAP0U4OnW@waldemar-brodkorb.de>
Waldemar, Sergey,
On 16/08/2026 14:43, Waldemar Brodkorb wrote:
> Hi,
>
> forgot to add Maintainer to CC.
>
> Waldemar Brodkorb wrote,
>
>> See here for a Changelog:
>> https://git.w1.fi/cgit/hostap/tree/wpa_supplicant/ChangeLog?id=e6386389448a4e0ec568fa7a27026e03f95bb768
>>
>> Security issues fixed in this release:
>> https://w1.fi/security/2026-4/incomplete-bounds-checking-of-mesh-ampe-messages-in-wpa_supplicant.txt
>> https://w1.fi/security/2026-3/unexpected-sae-commit-message-contents-terminating-wpa_suppliant.txt
>> https://w1.fi/security/2026-2/missing-network-context-validation-for-pmksa-caching.txt
>> https://w1.fi/security/2026-1/missing-ml-parsing-validation.txt
>>
>> Patches 0001 and 0002 are upstream.
>>
>> Tested on Raspberry PI4 (64 Bit).
>>
>> License changed:
>> -Copyright (c) 2002-2024, Jouni Malinen <j@w1.fi> and contributors
>> +Copyright (c) 2002-2026, Jouni Malinen <j@w1.fi> and contributors
>>
>> Signed-off-by: Waldemar Brodkorb <wbx@openadk.org>
>> ---
[...]
>> diff --git a/package/wpa_supplicant/wpa_supplicant.hash
>> b/package/wpa_supplicant/wpa_supplicant.hash
>> index 2f38dc257a..bea1e99b1f 100644
>> --- a/package/wpa_supplicant/wpa_supplicant.hash
>> +++ b/package/wpa_supplicant/wpa_supplicant.hash
>> @@ -1,3 +1,3 @@
>> # Locally calculated
>> -sha256
>> 912ea06f74e30a8e36fbb68064d6cdff218d8d591db0fc5d75dee6c81ac7fc0a
>> wpa_supplicant-2.11.tar.gz
>> -sha256
>> f1b5992bbdd015c3ccb7faaadd62ef58ed821e15b9329bf2ceb27511ccc3f562
>> README
>> +sha256
>> 08e23937e16d0155e55cab2b51f51fbe10d80a1aa91c4e15442645059b737ef6
>> wpa_supplicant-2.12.tar.gz
>> +sha256
>> 83be1b142c59ccf0d6c5dde0695d8f84dfba109bea058e78ec2942389ccf327f
>> README
>> diff --git a/package/wpa_supplicant/wpa_supplicant.mk
>> b/package/wpa_supplicant/wpa_supplicant.mk
>> index fe4bc34d55..93ac228947 100644
>> --- a/package/wpa_supplicant/wpa_supplicant.mk
>> +++ b/package/wpa_supplicant/wpa_supplicant.mk
>> @@ -4,7 +4,7 @@
>> #
>>
>> ################################################################################
>>
>> -WPA_SUPPLICANT_VERSION = 2.11
>> +WPA_SUPPLICANT_VERSION = 2.12
While testing, I was wondering if we shouldn't also update
hostapd to v2.12: https://w1.fi/hostapd/
What do you think?
>> WPA_SUPPLICANT_SITE = http://w1.fi/releases
>> WPA_SUPPLICANT_LICENSE = BSD-3-Clause
>> WPA_SUPPLICANT_LICENSE_FILES = README
>> --
>> 2.47.3
Best regards,
Julien.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2026-08-16 15:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-16 10:20 [Buildroot] [PATCH] package/wpa_supplicant: security bump to 2.12 Waldemar Brodkorb
2026-08-16 12:43 ` Waldemar Brodkorb
2026-08-16 15:49 ` Julien Olivain via buildroot [this message]
2026-08-16 13:11 ` Julien Olivain via buildroot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=baca04d491cacc42082435db7be33f74@free.fr \
--to=buildroot@buildroot.org \
--cc=geomatsi@gmail.com \
--cc=ju.o@free.fr \
--cc=wbx@openadk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox