Your message dated Thu, 29 Oct 2026 19:10:16 +0000
with message-id <[email protected]>
and subject line Bug#1149027: fixed in wpa 2:2.11-5
has caused the Debian Bug report #1149027,
regarding wpasupplicant: SIGSEGV in AP mode on any received DPP chirp; please 
backport upstream 9cb7b0bce to trixie
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
1149027: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1149027
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: wpasupplicant
Version: 2:2.10-24
Severity: important
Tags: patch upstream fixed-upstream

Dear Maintainer,

When wpa_supplicant runs an access point (mode=2 / AP mode, as NetworkManager's
"hotspot" or shared-mode Wi-Fi does), it crashes with SIGSEGV as soon as the AP
interface receives a DPP Presence Announcement ("chirp") from any nearby Wi-Fi
Easy Connect device. No interaction or association is needed: a nearby device
that chirps is enough. One wpa_supplicant usually serves every Wi-Fi interface,
so the crash also drops any client-mode connections, and it repeats on every
chirp (19 crashes in about 90 minutes in one field log).

Cause: in AP mode, wpa_supplicant hands received management frames to hostapd's
code (ap_mgmt_rx -> ieee802_11_mgmt -> hostapd_dpp_rx_action).
hostapd_dpp_rx_action
reads hapd->iface->interfaces->dpp, but wpa_supplicant's AP code never sets
iface->interfaces, so the read goes through NULL. Standalone hostapd sets it and
is not affected. The client-mode DPP path is not affected either.

Upstream fixed this in hostap commit 9cb7b0bce (2025-01-09, "DPP: Discard DPP
Action frame in AP mode if no global DPP context"), which adds a 4-line guard at
the top of hostapd_dpp_rx_action. It is in hostap 2.12. The commit names
e00f780e2 ("DPP2: hostapd as TCP Relay", 2019) as the cause, so 2.9 through 2.11
are affected. None of trixie 2:2.10-24, forky/sid 2:2.10-25 or experimental
2:2.11-2 carries it.

Upstream commit:
https://git.w1.fi/cgit/hostap/commit/?id=9cb7b0bce

Reproduction (two Debian trixie arm64 devices, Raspberry Pi OS):
 1. Device A: stock 2:2.10-24, NetworkManager AP on channel 6.
 2. Device B, on a Wi-Fi interface in client mode:
      wpa_cli -i <iface> dpp_bootstrap_gen type=qrcode
      wpa_cli -i <iface> dpp_chirp own=1 iter=1
 3. Device A logs "wlan0: DPP-RX src=<B> freq=2437 type=13" and wpa_supplicant
    segfaults in the same second; NetworkManager shows every Wi-Fi interface as
    supplicant-failed until it restarts.

With 9cb7b0bce applied to the 2:2.10-24 source as an extra debian/patches entry
(it applies with an offset), the same test sends 5+ chirps over 3.5 minutes with
no crash; the wpa_supplicant PID stays the same, and client-mode DPP on the
other interface still works. We have run that patched build on several devices
since 2026-09-14 with no side effects.

Since any nearby chirping device can repeatedly take down a Linux access point
built on wpa_supplicant, a backport to trixie (e.g. through a stable update)
would be appreciated.

Thank you.

--- End Message ---
--- Begin Message ---
Source: wpa
Source-Version: 2:2.11-5
Done: Andrej Shadura <[email protected]>

We believe that the bug you reported is fixed in the latest version of
wpa, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andrej Shadura <[email protected]> (supplier of updated wpa package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Thu, 29 Oct 2026 19:39:33 +0100
Source: wpa
Architecture: source
Version: 2:2.11-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Networking Team <[email protected]>
Changed-By: Andrej Shadura <[email protected]>
Closes: 1147955 1149027
Changes:
 wpa (2:2.11-5) unstable; urgency=medium
 .
   * Fix SIGSEGV in AP mode on any received DPP chirp (Closes: #1149027)
   * Fix SAE reporting over D-Bus (Closes: #1147955)
   * Disable MAC randomization during P2P provisioning.
Checksums-Sha1:
 fefc73a6df4c2b8b8e177e74d9db595a8216bd91 2906 wpa_2.11-5.dsc
 a21dfc8c82fa2cced754703b0f226043ac9d27d9 98912 wpa_2.11-5.debian.tar.xz
 fbd09cbf993b330eeae36bfce5d68c1d17c64b01 9075452 wpa_2.11-5.git.tar.xz
 60a01214d0b971b51dd5e4bc01e9013cb2fb3674 17719 wpa_2.11-5_source.buildinfo
Checksums-Sha256:
 7ba8cb468f21e45657097a73ec9dd7fe0463ca466345ab98bf1ec860cac378a2 2906 
wpa_2.11-5.dsc
 0e4ec38c169e0d3a585a5092ad3f0e9b7e1e967645f28abacffdbde40373170a 98912 
wpa_2.11-5.debian.tar.xz
 f6af9a1476859f28b3da27ed3a750f3c7719a1789bb30a2dca365dd4fd513e89 9075452 
wpa_2.11-5.git.tar.xz
 23b0eb534c7a7035ccc58ed22ed97e4a2228191d00596136cd1238daa9854c60 17719 
wpa_2.11-5_source.buildinfo
Files:
 96ee6ef9e7ac530b4c96b3b7a020bf35 2906 net optional wpa_2.11-5.dsc
 a2d4879336fff9e74ff603f80e62f496 98912 net optional wpa_2.11-5.debian.tar.xz
 79e0040ffa931a77bbcb384f22be7eac 9075452 net optional wpa_2.11-5.git.tar.xz
 0c5e29ea30f56ec13c48ea5de22715e1 17719 net optional wpa_2.11-5_source.buildinfo
Git-Tag-Info: tag=21e8aa5004a858c9fd8964dde1c5b0531ef7a4f8 
fp=83dcd17f44b22cc83656eda1e8446b4ac8c77261
Git-Tag-Tagger: Andrej Shadura <[email protected]>

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEN02M5NuW6cvUwJcqYG0ITkaDwHkFAmrjk1wACgkQYG0ITkaD
wHnN8Q/+I2JA3+R/YlvzbAvZxPPigrc+ahc/J2K1Y3ZFqwTNoEhrcCqc8oXW+CKa
vs7oFDK8X8izYqrEFuDygKS7yEZumJhlcbYMDaN7AT5V8dSssq6UL4S5wKTUWd7V
ikrAl8EOfV2GRkLv8oMvIFB2LrmcaXsn0ARYCbaoUEJBDZDznHrLNb2qL5cSOYAT
ucZ3AZEjpwi47nzoxHqb3o1eyAAcR/q2jgGN9v/3vnPUd9GuCzqcz/LZOJkwvz4o
GPKAzIKxy6/6G1l0wRtPddgFhpDpanoT/9fkiPEObzKZ+xPA0GPKnjOQO2mod6tn
ppdhnrFVtvNALKo5dSHEG9vCfHQSgZOa/aXLRPTL1IW6azWFVsUeJ92iuDPUSw65
P2nSZ215OTz6UUdgPJSnlaOfrXOUanny1HHtoLPtr3k7tZzDm3UQdgJgYrw2HAvj
UTF+IFwPqCwCtOlwHCGqMUwFeKh1DtA1GMOBELhACAsV6SbbSm19yiZrvgEZP813
5fIt5KvfEdBns/13dfFNsIekRTTRsBpFFXmHH8Q1vB6gEdbUJwHlkV+xen08U4ly
xes5jpXLDOa3uco0A1hc6+SJIVpz7Y9uVegagbwoiGR75KvWhiwmFTUe1YC6sNr3
NkhEoO3rTZ7gL7lKbZTt7Z3nzeKhJZ1uHtqAlW2TcLHUTpuevJk=
=38J5
-----END PGP SIGNATURE-----

Attachment: pgp4zkaRbuFpe.pgp
Description: PGP signature


--- End Message ---

Reply via email to