sctp: prevent reading out-of-bounds memory
Subsystems (3)
PATCH 1/1 sctp: prevent reading out-of-bounds memory
From: Dan Rosenberg <[email protected]>
Two user-controlled allocations in SCTP are subsequently dereferenced as sockaddr structs, without checking if the dereferenced struct members fall beyond the end of the allocated chunk. There doesn't appear to be any information leakage here based on how these members are used and additional checking, but it's still worth fixing.
---
net/sctp/socket.c | 13 ++++++++++++- 1 file changed, 12 insertions(+), 1 deletion(-)
net/sctp/socket.c renamed from net/sctp/socket.c~sctp-prevent-reading-out-of-bounds-memory +12 -1
@@ -918,6 +918,11 @@ SCTP_STATIC int sctp_setsockopt_bindx(st/* Walk through the addrs buffer and count the number of addresses. */ addr_buf = kaddrs;while (walk_size < addrs_size) { +if (walk_size +sizeof (sa_family_t) > addrs_size) { +kfree (kaddrs); +return -EINVAL ; + } + sa_addr = (struct sockaddr *)addr_buf; af =sctp_get_af_specific (sa_addr->sa_family);
@@ -1004,9 +1009,13 @@ static int __sctp_connect(struct sock* s/* Walk through the addrs buffer and count the number of addresses. */ addr_buf = kaddrs;while (walk_size < addrs_size) { +if (walk_size +sizeof (sa_family_t) > addrs_size) { + err = -EINVAL ; + goto out_free; + } + sa_addr = (union sctp_addr *)addr_buf; af =sctp_get_af_specific (sa_addr->sa.sa_family); - port =ntohs (sa_addr->v4.sin_port);/* If the address family is not supported or if this address * causes the address buffer to overflow return EINVAL.
@@ -1016,6 +1025,8 @@ static int __sctp_connect(struct sock* s goto out_free; } + port =ntohs (sa_addr->v4.sin_port); +/* Save current address so we can work with it */ memcpy (&to, sa_addr, af->sockaddr_len);
_
From: [email protected]
Date: Fri, 01 Oct 2010 14:16:58 -0700
Quoted 8 lines
From: Dan Rosenberg <[email protected]>
Two user-controlled allocations in SCTP are subsequently dereferenced as sockaddr structs, without checking if the dereferenced struct members fall beyond the end of the allocated chunk. There doesn't appear to be any information leakage here based on how these members are used and additional checking, but it's still worth fixing.
Quoted 5 lines
[[email protected]: remove unfashionable newlines, fix gmail tab->space conversion]Signed-off-by Dan Rosenberg <[email protected]>Acked-by Vlad Yasevich <[email protected]>Cc David Miller <[email protected]>Signed-off-by Andrew Morton <[email protected]>
Applied.