From: Patrick McHardy <kaber@trash.net>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH] netfilter: nft_rbtree: fix chain use underflow with intervals and map
Date: Thu, 6 Feb 2014 16:08:57 +0000 [thread overview]
Message-ID: <20140206160857.GA24151@macbook.localnet> (raw)
In-Reply-To: <1391702434-4103-1-git-send-email-pablo@netfilter.org>
On Thu, Feb 06, 2014 at 05:00:34PM +0100, Pablo Neira Ayuso wrote:
> If you add a rule using intervals+map that introduces a loop, the
> error path of the rbtree set decrements the chain refcount for each
> side of the interval, leading to a chain use counter underflow.
>
> Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>
> ---
> net/netfilter/nft_rbtree.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/net/netfilter/nft_rbtree.c b/net/netfilter/nft_rbtree.c
> index ca0c1b2..b18e88b 100644
> --- a/net/netfilter/nft_rbtree.c
> +++ b/net/netfilter/nft_rbtree.c
> @@ -69,8 +69,10 @@ static void nft_rbtree_elem_destroy(const struct nft_set *set,
> struct nft_rbtree_elem *rbe)
> {
> nft_data_uninit(&rbe->key, NFT_DATA_VALUE);
> - if (set->flags & NFT_SET_MAP)
> + if (set->flags & NFT_SET_MAP &&
> + !(rbe->flags & NFT_SET_ELEM_INTERVAL_END))
> nft_data_uninit(rbe->data, set->dtype);
> +
That can't be correct. The NFT_SET_ELEM_INTERVAL_END can at the same
time begin a new interval, so this code is supposed to be like this.
There can also only be a chain reference here if we took one before
during initialization.
Please provide a test case so I can try myself.
next prev parent reply other threads:[~2014-02-06 16:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-06 16:00 [PATCH] netfilter: nft_rbtree: fix chain use underflow with intervals and map Pablo Neira Ayuso
2014-02-06 16:08 ` Patrick McHardy [this message]
2014-02-06 16:28 ` Pablo Neira Ayuso
2014-02-06 17:17 ` Patrick McHardy
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=20140206160857.GA24151@macbook.localnet \
--to=kaber@trash.net \
--cc=netfilter-devel@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).