aboutsummaryrefslogtreecommitdiffstats
path: root/wpa_supplicant/events.c
diff options
context:
space:
mode:
authorJouni Malinen <j@w1.fi>2013-08-25 16:46:57 (GMT)
committerJouni Malinen <j@w1.fi>2013-08-25 16:46:57 (GMT)
commit25a8f9e316013ee65aafe1d2c8ea276f5e77da42 (patch)
treecdfaeb1291c91d604c9c50962f8dd41341d61270 /wpa_supplicant/events.c
parent0185007c2e2e79dc4c156d5e4ff354b9dadf1374 (diff)
downloadhostap-25a8f9e316013ee65aafe1d2c8ea276f5e77da42.zip
hostap-25a8f9e316013ee65aafe1d2c8ea276f5e77da42.tar.gz
hostap-25a8f9e316013ee65aafe1d2c8ea276f5e77da42.tar.bz2
Clear EAPOL supplicant configuration info on current_ssid changes
There were some code paths that allowed obsolete configuration data pointer to be maintained within EAPOL supplicant in case a network was removed while not connection to it (i.e., wpa_s->current_ssid not pointing to the network that was removed). This could result in use of freed memory, e.g., from eap_sm_notify_ctrl_attached() when a new control interface connected prior to the EAPOL supplicant configuration pointer got updated. Signed-hostap: Jouni Malinen <j@w1.fi>
Diffstat (limited to 'wpa_supplicant/events.c')
-rw-r--r--wpa_supplicant/events.c1
1 files changed, 1 insertions, 0 deletions
diff --git a/wpa_supplicant/events.c b/wpa_supplicant/events.c
index 3ecb0ce..40c6adf 100644
--- a/wpa_supplicant/events.c
+++ b/wpa_supplicant/events.c
@@ -187,6 +187,7 @@ void wpa_supplicant_mark_disassoc(struct wpa_supplicant *wpa_s)
eapol_sm_notify_eap_success(wpa_s->eapol, FALSE);
wpa_s->ap_ies_from_associnfo = 0;
wpa_s->current_ssid = NULL;
+ eapol_sm_notify_config(wpa_s->eapol, NULL, NULL);
wpa_s->key_mgmt = 0;
}