From: Xin Long <lucien.xin@gmail.com> Date: 2018-01-15 09:02:08
The check in sctp_sockaddr_af is not robust enough to forbid binding a
v4mapped v6 addr on a v4 socket.
The worse thing is that v4 socket's bind_verify would not convert this
v4mapped v6 addr to a v4 addr. syzbot even reported a crash as the v4
socket bound a v6 addr.
This patch is to fix it by doing the common sa.sa_family check first,
then AF_INET check for v4mapped v6 addrs.
Fixes: 7dab83de50c7 ("sctp: Support ipv6only AF_INET6 sockets.")
Reported-by: syzbot+7b7b518b1228d2743963@syzkaller.appspotmail.com
Acked-by: Neil Horman <nhorman@tuxdriver.com>
Signed-off-by: Xin Long <lucien.xin@gmail.com>
---
net/sctp/socket.c | 14 ++++++--------
1 file changed, 6 insertions(+), 8 deletions(-)
@@ -335,16 +335,14 @@ static struct sctp_af *sctp_sockaddr_af(struct sctp_sock *opt,if(len<sizeof(structsockaddr))returnNULL;+if(!opt->pf->af_supported(addr->sa.sa_family,opt))+returnNULL;+/* V4 mapped address are really of AF_INET family */if(addr->sa.sa_family==AF_INET6&&-ipv6_addr_v4mapped(&addr->v6.sin6_addr)){-if(!opt->pf->af_supported(AF_INET,opt))-returnNULL;-}else{-/* Does this PF support this AF? */-if(!opt->pf->af_supported(addr->sa.sa_family,opt))-returnNULL;-}+ipv6_addr_v4mapped(&addr->v6.sin6_addr)&&+!opt->pf->af_supported(AF_INET,opt))+returnNULL;/* If we get this far, af is valid. */af=sctp_get_af_specific(addr->sa.sa_family);
On Mon, Jan 15, 2018 at 05:02:00PM +0800, Xin Long wrote:
The check in sctp_sockaddr_af is not robust enough to forbid binding a
v4mapped v6 addr on a v4 socket.
The worse thing is that v4 socket's bind_verify would not convert this
v4mapped v6 addr to a v4 addr. syzbot even reported a crash as the v4
socket bound a v6 addr.
This patch is to fix it by doing the common sa.sa_family check first,
then AF_INET check for v4mapped v6 addrs.
Fixes: 7dab83de50c7 ("sctp: Support ipv6only AF_INET6 sockets.")
Reported-by: syzbot+7b7b518b1228d2743963@syzkaller.appspotmail.com
Acked-by: Neil Horman <nhorman@tuxdriver.com>
Signed-off-by: Xin Long <lucien.xin@gmail.com>
@@ -335,16 +335,14 @@ static struct sctp_af *sctp_sockaddr_af(struct sctp_sock *opt,if(len<sizeof(structsockaddr))returnNULL;+if(!opt->pf->af_supported(addr->sa.sa_family,opt))+returnNULL;+/* V4 mapped address are really of AF_INET family */if(addr->sa.sa_family==AF_INET6&&-ipv6_addr_v4mapped(&addr->v6.sin6_addr)){-if(!opt->pf->af_supported(AF_INET,opt))-returnNULL;-}else{-/* Does this PF support this AF? */-if(!opt->pf->af_supported(addr->sa.sa_family,opt))-returnNULL;-}+ipv6_addr_v4mapped(&addr->v6.sin6_addr)&&+!opt->pf->af_supported(AF_INET,opt))+returnNULL;/* If we get this far, af is valid. */af=sctp_get_af_specific(addr->sa.sa_family);
--
2.1.0
--
To unsubscribe from this list: send the line "unsubscribe linux-sctp" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
From: David Miller <davem@davemloft.net> Date: 2018-01-16 19:25:20
From: Xin Long <lucien.xin@gmail.com>
Date: Mon, 15 Jan 2018 17:02:00 +0800
The check in sctp_sockaddr_af is not robust enough to forbid binding a
v4mapped v6 addr on a v4 socket.
The worse thing is that v4 socket's bind_verify would not convert this
v4mapped v6 addr to a v4 addr. syzbot even reported a crash as the v4
socket bound a v6 addr.
This patch is to fix it by doing the common sa.sa_family check first,
then AF_INET check for v4mapped v6 addrs.
Fixes: 7dab83de50c7 ("sctp: Support ipv6only AF_INET6 sockets.")
Reported-by: syzbot+7b7b518b1228d2743963@syzkaller.appspotmail.com
Acked-by: Neil Horman <nhorman@tuxdriver.com>
Signed-off-by: Xin Long <lucien.xin@gmail.com>