From: Kuniyuki Iwashima <kuniyu@amazon.com>
To: <luwei32@huawei.com>
Cc: <asml.silence@gmail.com>, <ast@kernel.org>, <davem@davemloft.net>,
<dsahern@kernel.org>, <edumazet@google.com>,
<imagedong@tencent.com>, <kuba@kernel.org>, <kuniyu@amazon.com>,
<linux-kernel@vger.kernel.org>, <martin.lau@kernel.org>,
<ncardwell@google.com>, <netdev@vger.kernel.org>,
<pabeni@redhat.com>, <yoshfuji@linux-ipv6.org>
Subject: Re: [PATCH -next,v2] tcp: fix a signed-integer-overflow bug in tcp_add_backlog()
Date: Thu, 20 Oct 2022 13:57:30 -0700 [thread overview]
Message-ID: <20221020205730.10875-1-kuniyu@amazon.com> (raw)
In-Reply-To: <20221020143201.339599-1-luwei32@huawei.com>
Hi,
The subject should be
[PATCH net v2] tcp: ....
so that this patch will be backported to the stable tree.
From: Lu Wei <luwei32@huawei.com>
Date: Thu, 20 Oct 2022 22:32:01 +0800
> The type of sk_rcvbuf and sk_sndbuf in struct sock is int, and
> in tcp_add_backlog(), the variable limit is caculated by adding
> sk_rcvbuf, sk_sndbuf and 64 * 1024, it may exceed the max value
> of int and overflow. This patch limits sk_rcvbuf and sk_sndbuf
> to 0x7fff000 and transfers them to u32 to avoid signed-integer
> overflow.
>
> Fixes: c9c3321257e1 ("tcp: add tcp_add_backlog()")
> Signed-off-by: Lu Wei <luwei32@huawei.com>
> ---
> include/net/sock.h | 5 +++++
> net/core/sock.c | 10 ++++++----
> net/ipv4/tcp_ipv4.c | 3 ++-
> 3 files changed, 13 insertions(+), 5 deletions(-)
>
> diff --git a/include/net/sock.h b/include/net/sock.h
> index 9e464f6409a7..cc2d6c4047c2 100644
> --- a/include/net/sock.h
> +++ b/include/net/sock.h
> @@ -2529,6 +2529,11 @@ static inline void sk_wake_async(const struct sock *sk, int how, int band)
> #define SOCK_MIN_SNDBUF (TCP_SKB_MIN_TRUESIZE * 2)
> #define SOCK_MIN_RCVBUF TCP_SKB_MIN_TRUESIZE
>
> +/* limit sk_sndbuf and sk_rcvbuf to 0x7fff0000 to prevent overflow
> + * when adding sk_sndbuf, sk_rcvbuf and 64K in tcp_add_backlog()
> + */
> +#define SOCK_MAX_SNDRCVBUF (INT_MAX - 0xFFFF)
Should we apply this limit in tcp_rcv_space_adjust() ?
int rcvmem, rcvbuf;
...
rcvbuf = min_t(u64, rcvwin * rcvmem,
READ_ONCE(sock_net(sk)->ipv4.sysctl_tcp_rmem[2]));
if (rcvbuf > sk->sk_rcvbuf) {
WRITE_ONCE(sk->sk_rcvbuf, rcvbuf);
...
}
We still have 64K space if sk_rcvbuf were INT_MAX here though.
> +
> static inline void sk_stream_moderate_sndbuf(struct sock *sk)
> {
> u32 val;
> diff --git a/net/core/sock.c b/net/core/sock.c
> index a3ba0358c77c..33acc5e71100 100644
> --- a/net/core/sock.c
> +++ b/net/core/sock.c
> @@ -950,7 +950,7 @@ static void __sock_set_rcvbuf(struct sock *sk, int val)
> /* Ensure val * 2 fits into an int, to prevent max_t() from treating it
> * as a negative value.
> */
> - val = min_t(int, val, INT_MAX / 2);
> + val = min_t(int, val, SOCK_MAX_SNDRCVBUF / 2);
> sk->sk_userlocks |= SOCK_RCVBUF_LOCK;
>
> /* We double it on the way in to account for "struct sk_buff" etc.
> @@ -1142,7 +1142,7 @@ int sk_setsockopt(struct sock *sk, int level, int optname,
> /* Ensure val * 2 fits into an int, to prevent max_t()
> * from treating it as a negative value.
> */
> - val = min_t(int, val, INT_MAX / 2);
> + val = min_t(int, val, SOCK_MAX_SNDRCVBUF / 2);
> sk->sk_userlocks |= SOCK_SNDBUF_LOCK;
> WRITE_ONCE(sk->sk_sndbuf,
> max_t(int, val * 2, SOCK_MIN_SNDBUF));
> @@ -3365,8 +3365,10 @@ void sock_init_data(struct socket *sock, struct sock *sk)
> timer_setup(&sk->sk_timer, NULL, 0);
>
> sk->sk_allocation = GFP_KERNEL;
> - sk->sk_rcvbuf = READ_ONCE(sysctl_rmem_default);
> - sk->sk_sndbuf = READ_ONCE(sysctl_wmem_default);
> + sk->sk_rcvbuf = min_t(int, SOCK_MAX_SNDRCVBUF,
> + READ_ONCE(sysctl_rmem_default));
> + sk->sk_sndbuf = min_t(int, SOCK_MAX_SNDRCVBUF,
> + READ_ONCE(sysctl_wmem_default));
> sk->sk_state = TCP_CLOSE;
> sk_set_socket(sk, sock);
>
> diff --git a/net/ipv4/tcp_ipv4.c b/net/ipv4/tcp_ipv4.c
> index 7a250ef9d1b7..5340733336a6 100644
> --- a/net/ipv4/tcp_ipv4.c
> +++ b/net/ipv4/tcp_ipv4.c
> @@ -1878,7 +1878,8 @@ bool tcp_add_backlog(struct sock *sk, struct sk_buff *skb,
> * to reduce memory overhead, so add a little headroom here.
> * Few sockets backlog are possibly concurrently non empty.
> */
> - limit = READ_ONCE(sk->sk_rcvbuf) + READ_ONCE(sk->sk_sndbuf) + 64*1024;
> + limit = (u32)READ_ONCE(sk->sk_rcvbuf) +
> + (u32)READ_ONCE(sk->sk_sndbuf) + 64*1024;
nit: s/64*1024/64 * 1024/
$ git show --format=email | ./scripts/checkpatch.pl
CHECK: spaces preferred around that '*' (ctx:VxV)
#79: FILE: net/ipv4/tcp_ipv4.c:1882:
+ (u32)READ_ONCE(sk->sk_sndbuf) + 64*1024;
^
>
> if (unlikely(sk_add_backlog(sk, skb, limit))) {
> bh_unlock_sock(sk);
> --
> 2.31.1
next prev parent reply other threads:[~2022-10-20 20:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-20 14:32 [PATCH -next,v2] tcp: fix a signed-integer-overflow bug in tcp_add_backlog() Lu Wei
2022-10-20 20:57 ` Kuniyuki Iwashima [this message]
2022-10-20 23:15 ` Eric Dumazet
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=20221020205730.10875-1-kuniyu@amazon.com \
--to=kuniyu@amazon.com \
--cc=asml.silence@gmail.com \
--cc=ast@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=imagedong@tencent.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luwei32@huawei.com \
--cc=martin.lau@kernel.org \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=yoshfuji@linux-ipv6.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