From: Florian Westphal <fw@strlen.de>
To: Dave Jones <davej@codemonkey.org.uk>
Cc: netfilter-devel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: iptables: ensure number of counters is >0 in do_replace()
Date: Wed, 20 May 2015 01:19:50 +0200 [thread overview]
Message-ID: <20150519231950.GA30845@breakpoint.cc> (raw)
In-Reply-To: <20150519231120.GA1761@codemonkey.org.uk>
Dave Jones <davej@codemonkey.org.uk> wrote:
> After improving setsockopt() coverage in trinity, I started triggering
> vmalloc failures pretty reliably from this code path:
>
> warn_alloc_failed+0xe9/0x140
> __vmalloc_node_range+0x1be/0x270
> vzalloc+0x4b/0x50
> __do_replace+0x52/0x260 [ip_tables]
> do_ipt_set_ctl+0x15d/0x1d0 [ip_tables]
> nf_setsockopt+0x65/0x90
> ip_setsockopt+0x61/0xa0
> raw_setsockopt+0x16/0x60
> sock_common_setsockopt+0x14/0x20
> SyS_setsockopt+0x71/0xd0
>
> It turns out we don't validate that the num_counters field in the
> struct we pass in from userspace is initialized.
>
> Signed-off-by: Dave Jones <davej@codemonkey.org.uk>
>
> diff --git a/net/ipv4/netfilter/ip_tables.c b/net/ipv4/netfilter/ip_tables.c
> index c69db7fa25ee..12a33d178614 100644
> --- a/net/ipv4/netfilter/ip_tables.c
> +++ b/net/ipv4/netfilter/ip_tables.c
> @@ -1262,6 +1262,9 @@ do_replace(struct net *net, const void __user *user, unsigned int len)
> /* overflow check */
> if (tmp.num_counters >= INT_MAX / sizeof(struct xt_counters))
> return -ENOMEM;
> + if (tmp.num_counters == 0)
> + return -EINVAL;
> +
Good catch. Due to iptables wonderful copy-paste programming model,
this also needs fixing in compat_do_replace, ip6tables, arbtables and
ebtables (8 different places, ick).
next prev parent reply other threads:[~2015-05-19 23:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-19 23:11 iptables: ensure number of counters is >0 in do_replace() Dave Jones
2015-05-19 23:19 ` Florian Westphal [this message]
2015-05-19 23:42 ` Dave Jones
2015-05-20 0:20 ` David Miller
2015-05-20 0:55 ` netfilter: " Dave Jones
2015-05-21 11:42 ` 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=20150519231950.GA30845@breakpoint.cc \
--to=fw@strlen.de \
--cc=davej@codemonkey.org.uk \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.