netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: valdis.kletnieks@vt.edu
To: Florian Westphal <fw@strlen.de>, Pablo Neira Ayuso <pablo@netfilter.org>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: linux-next: ip6tables *broken* - last base chain position %u doesn't match underflow %u (hook %u
Date: Tue, 20 Mar 2018 11:17:33 -0400	[thread overview]
Message-ID: <24374.1521559053@turing-police.cc.vt.edu> (raw)

[-- Attachment #1: Type: text/plain, Size: 2255 bytes --]

(Resending because I haven't heard anything)

Am hitting an issue with this commit:

commit 0d7df906a0e78079a02108b06d32c3ef2238ad25
Author: Florian Westphal <fw@strlen.de>
Date:   Tue Feb 27 19:42:37 2018 +0100

    netfilter: x_tables: ensure last rule in base chain matches underflow/policy

This trips on my system:

[   64.402790] ip6_tables: last base chain position 1136 doesn't match underflow 1344 (hook 1)

More annoyingly, the return value means that ip6tables aren't initialized
so there's no firewall protection.  (In other words, this:

    If a (syzkaller generated) ruleset doesn't have the underflow/policy
    stored as the last rule in the base chain, then iptables will abort()
    because it doesn't find the chain policy.

ends up meaning iptables aborts anyhow.

My iptables isn't syzkaller generated - it's mostly crufty vi-generated. ;)

Messages generated as I tried to build smaller tables to narrow down the problem:
(not sure where it gets the numbers from, as I reduced it from 50 lines down to 3
and no real correlation to the tables I was trying to load - in particular the numbers
went up once and remained unchanged once, even though between each try I was
whacking out another 5-10 lines...)

[   64.402790] ip6_tables: last base chain position 1136 doesn't match underflow 1344 (hook 1)
[ 1897.914828] ip6_tables: last base chain position 928 doesn't match underflow 1136 (hook 1)
[ 1954.032735] ip6_tables: last base chain position 720 doesn't match underflow 928 (hook 1)
[ 2021.813719] ip6_tables: last base chain position 920 doesn't match underflow 1128 (hook 1)
[ 2035.044103] ip6_tables: last base chain position 920 doesn't match underflow 1128 (hook 1)
[ 2060.594412] ip6_tables: last base chain position 616 doesn't match underflow 824 (hook 1)

I finally got /etc/sysconfig/ip6tables down to this:

# Generated by ip6tables-save v1.6.2 on Thu Mar  8 08:20:04 2018
*filter
:INPUT ACCEPT [0:0]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [208207395:46346275671]
[120166037:34218429901] -A INPUT -i lo+ -j ACCEPT
[129329499:129691207309] -A INPUT -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT
[0:0] -A INPUT -j DROP
COMMIT
# Completed on Thu Mar  8 08:20:04 2018

About as minimal as it can get. :)

Any ideas?

[-- Attachment #2: Type: application/pgp-signature, Size: 486 bytes --]

             reply	other threads:[~2018-03-20 15:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-20 15:17 valdis.kletnieks [this message]
2018-03-20 15:48 ` linux-next: ip6tables *broken* - last base chain position %u doesn't match underflow %u (hook %u Florian Westphal
2018-03-20 15:57   ` valdis.kletnieks

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=24374.1521559053@turing-police.cc.vt.edu \
    --to=valdis.kletnieks@vt.edu \
    --cc=fw@strlen.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pablo@netfilter.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;
as well as URLs for NNTP newsgroup(s).