From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eric Dumazet Subject: Re: [PATCH net] netfilter: xt_hashlimit: do not allow empty names Date: Sun, 28 Jan 2018 09:54:05 -0800 Message-ID: <1517162045.3715.78.camel@gmail.com> References: <1517154099.3715.77.camel@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8bit Cc: Jozsef Kadlecsik , Florian Westphal , netfilter-devel@vger.kernel.org, netdev To: Pablo Neira Ayuso Return-path: Received: from mail-pl0-f67.google.com ([209.85.160.67]:45278 "EHLO mail-pl0-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751986AbeA1RyJ (ORCPT ); Sun, 28 Jan 2018 12:54:09 -0500 In-Reply-To: <1517154099.3715.77.camel@gmail.com> Sender: netdev-owner@vger.kernel.org List-ID: On Sun, 2018-01-28 at 07:41 -0800, Eric Dumazet wrote: > From: Eric Dumazet > > Syzbot reported a WARN() in proc_create_data() [1] > > Issue here is that xt_hashlimit does not check that user space provided > an empty table name. > Signed-off-by: Eric Dumazet > Reported-by: syzbot > --- >  net/netfilter/xt_hashlimit.c |    2 ++ >  1 file changed, 2 insertions(+) > > diff --git a/net/netfilter/xt_hashlimit.c b/net/netfilter/xt_hashlimit.c > index 5da8746f7b88ff4c9446f256e542e823a6a561b0..eae732e013df92a364b500645360d4606c283a75 100644 > --- a/net/netfilter/xt_hashlimit.c > +++ b/net/netfilter/xt_hashlimit.c > @@ -894,6 +894,8 @@ static int hashlimit_mt_check_common(const struct xt_mtchk_param *par, > return -ERANGE; > } > > + if (!name[0]) > + return -EINVAL; > mutex_lock(&hashlimit_mutex); > *hinfo = htable_find_get(net, name, par->family); > if (*hinfo == NULL) { I wonder if we should also check if name includes a '/' ? if (!name[0] || strchr(name, '/')) return -EINVAL;