The EAP-pwd implementation in hostapd (EAP server) before 2.8 and wpa_supplicant (EAP peer) before 2.8 does not validate fragmentation reassembly state properly for a case where an unexpected fragment could be received. This could result in process termination due to a NULL pointer dereference (denial of service). This affects eap_server/eap_server_pwd.c and eap_peer/eap_pwd.c.
https://www.openwall.com/lists/oss-security/2019/04/18/6
https://www.debian.org/security/2019/dsa-4450
https://w1.fi/security/2019-5/eap-pwd-message-reassembly-issue-with-unexpected-fragment.txt
https://w1.fi/security/2019-5/
https://usn.ubuntu.com/3969-2/
https://usn.ubuntu.com/3969-1/
https://security.gentoo.org/glsa/201908-25
https://security.FreeBSD.org/advisories/FreeBSD-SA-19:03.wpa.asc
https://seclists.org/bugtraq/2019/May/64
https://seclists.org/bugtraq/2019/May/40
https://lists.debian.org/debian-lts-announce/2019/07/msg00030.html