All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Bui Viet Dung <dungvn2345@gmail.com>
Cc: Florian Westphal <fw@strlen.de>, Phil Sutter <phil@nwl.cc>,
	netfilter-devel@vger.kernel.org, coreteam@netfilter.org,
	linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] netfilter: nft_set_pipapo: skip transaction elements during GC
Date: Wed, 7 Oct 2026 21:45:55 +0200	[thread overview]
Message-ID: <asahc6ypIusA4OBc@chamomile> (raw)
In-Reply-To: <20261007182057.332512-1-dungvn2345@gmail.com>

On Thu, Oct 08, 2026 at 01:20:57AM +0700, Bui Viet Dung wrote:
> Since nft_set_commit_update() runs set commit callbacks before processing
> NEWSETELEM transactions, pipapo_gc_scan() can observe elements added by
> the transaction being committed.
>
> The scan evaluates elements in priv->clone without checking the element's
> transaction state. Expired elements are deactivated, dropped from
> priv->clone, and queued for GC reclaim via pipapo_gc_queue().
> 
> When the transaction loop in nf_tables_commit() subsequently processes
> NFT_MSG_NEWSETELEM, it calls nft_setelem_activate() on an element pointer
> that has already been handed off to GC reclaim, causing a
> slab-use-after-free.

You cannot add expired elements.

Elements are either in two states when GC run before the transaction
is processed:

- New (not expired, never)
- Old (expired)

I guess this is triggering because of the rbtree fix, but that is
different issue, because "end interval" has no timeout extension.

> Only consider elements that are fully active in both generations, matching
> the fix applied to nft_set_rbtree in commit 86b6471e690c ("netfilter:
> nft_set_rbtree: skip transaction elements during GC"). Advance first_rule
> by rules_f0 before continuing so the loop proceeds to the next rule.
> 
> Fixes: 1e3b9e1c77fe ("netfilter: nf_tables: call set ops .commit when building new ruleset blob")
> Cc: stable@vger.kernel.org
> Signed-off-by: Bui Viet Dung <dungvn2345@gmail.com>
> ---
>  net/netfilter/nft_set_pipapo.c | 5 +++++
>  1 file changed, 5 insertions(+)
> 
> diff --git a/net/netfilter/nft_set_pipapo.c b/net/netfilter/nft_set_pipapo.c
> index 978bb0c0110..48658c09c59 100644
> --- a/net/netfilter/nft_set_pipapo.c
> +++ b/net/netfilter/nft_set_pipapo.c
> @@ -1745,6 +1745,11 @@ static void pipapo_gc_scan(struct nft_set *set, struct nft_pipapo_match *m)
>  		i--;
>  		e = f->mt[rulemap[i].to].e;
>  
> +		if (!nft_set_elem_active(&e->ext, NFT_GENMASK_ANY)) {
> +			first_rule += rules_f0;
> +			continue;
> +		}
> +
>  		/* synchronous gc never fails, there is no need to set on
>  		 * NFT_SET_ELEM_DEAD_BIT.
>  		 */
> -- 
> 2.43.0
> 

  reply	other threads:[~2026-10-07 19:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-07 18:20 [PATCH] netfilter: nft_set_pipapo: skip transaction elements during GC Bui Viet Dung
2026-10-07 19:45 ` Pablo Neira Ayuso [this message]
2026-10-08  9:05 ` Florian Westphal
2026-10-08 11:18 ` Bui Viet Dung

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=asahc6ypIusA4OBc@chamomile \
    --to=pablo@netfilter.org \
    --cc=coreteam@netfilter.org \
    --cc=dungvn2345@gmail.com \
    --cc=fw@strlen.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=phil@nwl.cc \
    --cc=stable@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.