From: "zhangxiaoxu (A)" <zhangxiaoxu5@huawei.com>
To: Simon Horman <horms@verge.net.au>
Cc: <wensong@linux-vs.org>, <ja@ssi.bg>, <netdev@vger.kernel.org>,
<lvs-devel@vger.kernel.org>,
Pablo Neira Ayuso <pablo@netfilter.org>
Subject: Re: [PATCH] ipvs: Fix signed integer overflow when setsockopt timeout
Date: Thu, 24 Jan 2019 20:22:04 +0800 [thread overview]
Message-ID: <b1b6d534-435a-0194-bc3a-a71dc1eb2d25@huawei.com> (raw)
In-Reply-To: <20190114121513.mgj45pt3rrgomrqo@verge.net.au>
ping.
On 1/14/2019 8:15 PM, Simon Horman wrote:
> On Thu, Jan 10, 2019 at 04:39:06PM +0800, ZhangXiaoxu wrote:
>> There is a UBSAN bug report as below:
>> UBSAN: Undefined behaviour in net/netfilter/ipvs/ip_vs_ctl.c:2227:21
>> signed integer overflow:
>> -2147483647 * 1000 cannot be represented in type 'int'
>>
>> Reproduce program:
>> #include <stdio.h>
>> #include <sys/types.h>
>> #include <sys/socket.h>
>>
>> #define IPPROTO_IP 0
>> #define IPPROTO_RAW 255
>>
>> #define IP_VS_BASE_CTL (64+1024+64)
>> #define IP_VS_SO_SET_TIMEOUT (IP_VS_BASE_CTL+10)
>>
>> /* The argument to IP_VS_SO_GET_TIMEOUT */
>> struct ipvs_timeout_t {
>> int tcp_timeout;
>> int tcp_fin_timeout;
>> int udp_timeout;
>> };
>>
>> int main() {
>> int ret = -1;
>> int sockfd = -1;
>> struct ipvs_timeout_t to;
>>
>> sockfd = socket(AF_INET, SOCK_RAW, IPPROTO_RAW);
>> if (sockfd == -1) {
>> printf("socket init error\n");
>> return -1;
>> }
>>
>> to.tcp_timeout = -2147483647;
>> to.tcp_fin_timeout = -2147483647;
>> to.udp_timeout = -2147483647;
>>
>> ret = setsockopt(sockfd,
>> IPPROTO_IP,
>> IP_VS_SO_SET_TIMEOUT,
>> (char *)(&to),
>> sizeof(to));
>>
>> printf("setsockopt return %d\n", ret);
>> return ret;
>> }
>>
>> Return -EINVAL if the timeout value is negative or max than 'INT_MAX / HZ'.
>>
>> Signed-off-by: ZhangXiaoxu <zhangxiaoxu5@huawei.com>
>
> Thanks, this looks good to me.
>
> Pablo, could you consider applying this to nf?
>
> Acked-by: Simon Horman <horms@verge.net.au>
>
>> ---
>> net/netfilter/ipvs/ip_vs_ctl.c | 13 +++++++++++++
>> 1 file changed, 13 insertions(+)
>>
>> diff --git a/net/netfilter/ipvs/ip_vs_ctl.c b/net/netfilter/ipvs/ip_vs_ctl.c
>> index 432141f..444aaca 100644
>> --- a/net/netfilter/ipvs/ip_vs_ctl.c
>> +++ b/net/netfilter/ipvs/ip_vs_ctl.c
>> @@ -2221,6 +2221,19 @@ static int ip_vs_set_timeout(struct netns_ipvs *ipvs, struct ip_vs_timeout_user
>> u->udp_timeout);
>>
>> #ifdef CONFIG_IP_VS_PROTO_TCP
>> + if (u->tcp_timeout < 0 || u->tcp_timeout > (INT_MAX / HZ) ||
>> + u->tcp_fin_timeout < 0 || u->tcp_fin_timeout > (INT_MAX / HZ)) {
>> + return -EINVAL;
>> + }
>> +#endif
>> +
>> +#ifdef CONFIG_IP_VS_PROTO_UDP
>> + if (u->udp_timeout < 0 || u->udp_timeout > (INT_MAX / HZ)) {
>> + return -EINVAL;
>> + }
>> +#endif
>> +
>> +#ifdef CONFIG_IP_VS_PROTO_TCP
>> if (u->tcp_timeout) {
>> pd = ip_vs_proto_data_get(ipvs, IPPROTO_TCP);
>> pd->timeout_table[IP_VS_TCP_S_ESTABLISHED]
>> --
>> 2.7.4
>>
>
> .
>
next prev parent reply other threads:[~2019-01-24 12:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-10 8:39 [PATCH] ipvs: Fix signed integer overflow when setsockopt timeout ZhangXiaoxu
2019-01-14 7:34 ` zhangxiaoxu (A)
2019-01-14 12:15 ` Simon Horman
2019-01-24 12:22 ` zhangxiaoxu (A) [this message]
2019-01-24 12:32 ` Pablo Neira Ayuso
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b1b6d534-435a-0194-bc3a-a71dc1eb2d25@huawei.com \
--to=zhangxiaoxu5@huawei.com \
--cc=horms@verge.net.au \
--cc=ja@ssi.bg \
--cc=lvs-devel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=wensong@linux-vs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox