[Bug 258527] wpa_supplicant(8) from the base is not able to bring up wlan(4) interface correctly due to SIGSEGV after EAP/PEAP MSCHAPv2 authentication

From: <bugzilla-noreply_at_freebsd.org>
Date: Fri, 17 Sep 2021 08:21:46 +0000
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=258527

--- Comment #8 from Marek Zarychta <zarychtam_at_plan-b.pwste.edu.pl> ---
(In reply to Cy Schubert from comment #7)
>Don't update your system.
Too late. I am now on stable/13-n247303-adfb7f807c6.

>Then try wpa_supplicant again and send me the dump.
I have a few, will send you email and share them. Here's one of them:

Reading symbols from /usr/sbin/wpa_supplicant...
Reading symbols from /usr/lib/debug//usr/sbin/wpa_supplicant.debug...
[New LWP 100330]
Core was generated by `/usr/sbin/wpa_supplicant -s -dd -B -i wlan0 -c
/etc/wpa_supplicant.conf -D bsd -'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x0000008000000076 in ?? ()
(gdb) bt
#0  0x0000008000000076 in ?? ()
#1  0x0000000000316d93 in wpa_sm_key_mgmt_set_pmk (sm=0x801012700, 
    pmk=0x801012700
"\354\350\206e\216\324\v\231ߞ\225\006\001\237\034N\355\362<h\034\204\342\222\330\367\354\023\272\305",
<incomplete sequence \365>, pmk_len=32) at
/usr/src/contrib/wpa/src/rsn_supp/wpa_i.h:393
#2  0x0000000000316cf4 in wpa_supplicant_key_mgmt_set_pmk (sm=0x801012700) at
/usr/src/contrib/wpa/src/rsn_supp/wpa.c:252
#3  0x000000000031674a in wpa_supplicant_get_pmk (sm=0x801012700,
src_addr=0x8010634a0 "", 
    pmkid=0x8010444e9 "b\217\306[r\346\032\264\327\375\231\331Z!WC") at
/usr/src/contrib/wpa/src/rsn_supp/wpa.c:374
#4  0x000000000031150a in wpa_supplicant_process_1_of_4 (sm=0x801012700,
src_addr=0x8010634a0 "", key=0x801044484, ver=2, 
    key_data=0x8010444e3 "\335\024", key_data_len=22) at
/usr/src/contrib/wpa/src/rsn_supp/wpa.c:621
#5  0x000000000030ffca in wpa_sm_rx_eapol (sm=0x801012700, src_addr=0x8010634a0
"", buf=0x8010634a8 "\001\003", len=121)
    at /usr/src/contrib/wpa/src/rsn_supp/wpa.c:2438
#6  0x00000000002b91e2 in wpa_supplicant_rx_eapol (ctx=0x801039000,
src_addr=0x8010634a0 "", buf=0x8010634a8 "\001\003", len=121)
    at /usr/src/contrib/wpa/wpa_supplicant/wpa_supplicant.c:4303
#7  0x0000000000308405 in l2_packet_receive (sock=6, eloop_ctx=0x801028be0,
sock_ctx=0x801060000)
    at /usr/src/contrib/wpa/src/l2_packet/l2_packet_freebsd.c:98
#8  0x0000000000367460 in eloop_sock_table_dispatch (table=0x3702a0 <eloop+8>,
fds=0x801044100) at /usr/src/contrib/wpa/src/utils/eloop.c:600
#9  0x00000000003670c2 in eloop_run () at
/usr/src/contrib/wpa/src/utils/eloop.c:1223
#10 0x00000000002bc515 in wpa_supplicant_run (global=0x80102d000) at
/usr/src/contrib/wpa/wpa_supplicant/wpa_supplicant.c:6526
#11 0x000000000029e5a1 in main (argc=12, argv=0x7fffffffebc0) at
/usr/src/contrib/wpa/wpa_supplicant/main.c:397
quit)

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Received on Fri Sep 17 2021 - 08:21:46 UTC

Original text of this message