EAP-pwd: Avoid double-frees on some error paths
At least some error paths (e.g., hitting the limit on hunt-and-peck iterations) could have resulted in double-freeing of some memory allocations. Avoid this by setting the pointers to NULL after they have been freed instead of trying to free the data structure in a location where some external references cannot be cleared. [Bug 453] Signed-hostap: Jouni Malinen <j@w1.fi>
This commit is contained in:
parent
0f27f15911
commit
8350d0afd8
2 changed files with 9 additions and 3 deletions
|
@ -252,11 +252,13 @@ int compute_password_element(EAP_PWD_group *grp, u16 num,
|
|||
if (0) {
|
||||
fail:
|
||||
EC_GROUP_free(grp->group);
|
||||
grp->group = NULL;
|
||||
EC_POINT_free(grp->pwe);
|
||||
grp->pwe = NULL;
|
||||
BN_free(grp->order);
|
||||
grp->order = NULL;
|
||||
BN_free(grp->prime);
|
||||
os_free(grp);
|
||||
grp = NULL;
|
||||
grp->prime = NULL;
|
||||
ret = 1;
|
||||
}
|
||||
/* cleanliness and order.... */
|
||||
|
|
|
@ -725,6 +725,7 @@ eap_pwd_process(struct eap_sm *sm, void *priv, struct eap_method_ret *ret,
|
|||
*/
|
||||
if (data->out_frag_pos >= wpabuf_len(data->outbuf)) {
|
||||
wpabuf_free(data->outbuf);
|
||||
data->outbuf = NULL;
|
||||
data->out_frag_pos = 0;
|
||||
}
|
||||
wpa_printf(MSG_DEBUG, "EAP-pwd: Send %s fragment of %d bytes",
|
||||
|
@ -856,8 +857,11 @@ eap_pwd_process(struct eap_sm *sm, void *priv, struct eap_method_ret *ret,
|
|||
/*
|
||||
* if we're not fragmenting then there's no need to carry this around
|
||||
*/
|
||||
if (data->out_frag_pos == 0)
|
||||
if (data->out_frag_pos == 0) {
|
||||
wpabuf_free(data->outbuf);
|
||||
data->outbuf = NULL;
|
||||
data->out_frag_pos = 0;
|
||||
}
|
||||
|
||||
return resp;
|
||||
}
|
||||
|
|
Loading…
Reference in a new issue