netfilter: x_tables: don't reject valid target size on some architectures
authorFlorian Westphal <fw@strlen.de>
Wed, 1 Jun 2016 00:04:44 +0000 (02:04 +0200)
committerSasha Levin <sasha.levin@oracle.com>
Tue, 12 Jul 2016 12:48:34 +0000 (08:48 -0400)
commitbbb7ecc8a2b66fa5422579409dbc18797984c8ea
tree7fc5c7888bf7daa95915c25bd94ea07fa6625577
parent3b94ada46f61938d9c49aa198fe560b1f8faea79
netfilter: x_tables: don't reject valid target size on some architectures

[ Upstream commit 7b7eba0f3515fca3296b8881d583f7c1042f5226 ]

Quoting John Stultz:
  In updating a 32bit arm device from 4.6 to Linus' current HEAD, I
  noticed I was having some trouble with networking, and realized that
  /proc/net/ip_tables_names was suddenly empty.
  Digging through the registration process, it seems we're catching on the:

   if (strcmp(t->u.user.name, XT_STANDARD_TARGET) == 0 &&
       target_offset + sizeof(struct xt_standard_target) != next_offset)
         return -EINVAL;

  Where next_offset seems to be 4 bytes larger then the
  offset + standard_target struct size.

next_offset needs to be aligned via XT_ALIGN (so we can access all members
of ip(6)t_entry struct).

This problem didn't show up on i686 as it only needs 4-byte alignment for
u64, but iptables userspace on other 32bit arches does insert extra padding.

Reported-by: John Stultz <john.stultz@linaro.org>
Tested-by: John Stultz <john.stultz@linaro.org>
Fixes: 7ed2abddd20cf ("netfilter: x_tables: check standard target size too")
Signed-off-by: Florian Westphal <fw@strlen.de>
Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>
Signed-off-by: Sasha Levin <sasha.levin@oracle.com>
net/netfilter/x_tables.c