sctp: validate from_addr_param return
Ilja reported that, simply putting it, nothing was validating that from_addr_param functions were operating on initialized memory. That is, the parameter itself was being validated by sctp_walk_params, but it doesn't check for types and their specific sizes and it could be a 0-length one, causing from_addr_param to potentially work over the next parameter or even uninitialized memory. The fix here is to, in all calls to from_addr_param, check if enough space is there for the wanted IP address type. Reported-by: Ilja Van Sprundel <ivansprundel@ioactive.com> Signed-off-by: Marcelo Ricardo Leitner <marcelo.leitner@gmail.com> Signed-off-by: David S. Miller <davem@davemloft.net>
This commit is contained in:
committed by
David S. Miller
parent
9ea3e52c5b
commit
0c5dc070ff
@@ -270,22 +270,19 @@ int sctp_raw_to_bind_addrs(struct sctp_bind_addr *bp, __u8 *raw_addr_list,
|
||||
rawaddr = (union sctp_addr_param *)raw_addr_list;
|
||||
|
||||
af = sctp_get_af_specific(param_type2af(param->type));
|
||||
if (unlikely(!af)) {
|
||||
if (unlikely(!af) ||
|
||||
!af->from_addr_param(&addr, rawaddr, htons(port), 0)) {
|
||||
retval = -EINVAL;
|
||||
sctp_bind_addr_clean(bp);
|
||||
break;
|
||||
goto out_err;
|
||||
}
|
||||
|
||||
af->from_addr_param(&addr, rawaddr, htons(port), 0);
|
||||
if (sctp_bind_addr_state(bp, &addr) != -1)
|
||||
goto next;
|
||||
retval = sctp_add_bind_addr(bp, &addr, sizeof(addr),
|
||||
SCTP_ADDR_SRC, gfp);
|
||||
if (retval) {
|
||||
if (retval)
|
||||
/* Can't finish building the list, clean up. */
|
||||
sctp_bind_addr_clean(bp);
|
||||
break;
|
||||
}
|
||||
goto out_err;
|
||||
|
||||
next:
|
||||
len = ntohs(param->length);
|
||||
@@ -294,6 +291,12 @@ next:
|
||||
}
|
||||
|
||||
return retval;
|
||||
|
||||
out_err:
|
||||
if (retval)
|
||||
sctp_bind_addr_clean(bp);
|
||||
|
||||
return retval;
|
||||
}
|
||||
|
||||
/********************************************************************
|
||||
|
||||
Reference in New Issue
Block a user