From: "Jérémy Jean" <jeremy.jean@oss.cyber.gouv.fr>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: Florian Westphal <fw@strlen.de>, Phil Sutter <phil@nwl.cc>,
netfilter-devel@vger.kernel.org, coreteam@netfilter.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH nf] netfilter: nft_set_rbtree: reject expired interval ends
Date: Tue, 06 Oct 2026 15:17:06 +0200 [thread overview]
Message-ID: <9a9f2587b7bd37c8d03d0105cf968b25@oss.cyber.gouv.fr> (raw)
In-Reply-To: <asQtPfgYhK1uxMpR@chamomile>
On 2026-10-06 01:05, Pablo Neira Ayuso wrote:
> Hi,
>
> On Mon, Oct 05, 2026 at 08:04:05PM +0000, Jérémy Jean wrote:
>> Consider two ranges in a netfilter verdict map:
>> * keys 10-19 accept packets, and
>> * keys 30-39 jump to chain 'victim'.
>> Now, delete the end marker at 20. The lookup array now uses element 30
>> as the first range's end, so an INTERVAL_END query for key 15 returns
>> element 30, including its jump verdict and chain pointer. This can
>> make
>> KASAN reports a UAF after the GC releases reference chain for 30 that
>> has expired:
>>
>> BUG: KASAN: slab-use-after-free in nft_verdict_dump+0xdd/0x110
>> Read of size 8 at addr ff110000009dfb58 by task repro/50
>> ...
>> Call Trace:
>> ...
>> nft_verdict_dump+0xdd/0x110
>> nft_data_dump+0x4d/0x80
>> nf_tables_fill_setelem+0x30b/0x8a0
>> ? __asan_memcpy+0x3c/0x60
>> nf_tables_fill_setelem_info+0x1b0/0x200
>> nft_get_set_elem+0x3fd/0x4b0
>> ...
>> Freed by task 24:
>> ...
>> kfree+0x1a5/0x280
>> nf_tables_trans_destroy_work+0x2cb/0x520
>>
>> Reject expired endpoints in nft_rbtree_get() before returning them.
>>
>> Fixes: 2aa34191f06f ("netfilter: nft_set_rbtree: use binary search
>> array in get command")
>> Cc: stable@vger.kernel.org
>> Assisted-by: LLM
>> Signed-off-by: Jérémy Jean <Jeremy.Jean@oss.cyber.gouv.fr>
>> ---
>> net/netfilter/nft_set_rbtree.c | 2 ++
>> 1 file changed, 2 insertions(+)
>>
>> diff --git a/net/netfilter/nft_set_rbtree.c
>> b/net/netfilter/nft_set_rbtree.c
>> index 9894832..1fd9cbe 100644
>> --- a/net/netfilter/nft_set_rbtree.c
>> +++ b/net/netfilter/nft_set_rbtree.c
>> @@ -187,6 +187,8 @@ nft_rbtree_get(const struct net *net, const struct
>> nft_set *set,
>> if (flags & NFT_SET_ELEM_INTERVAL_END) {
>> if (!interval->to)
>> return NULL;
>> + if (nft_set_elem_expired(interval->to))
>> + return ERR_PTR(-ENOENT);
>>
>> rbe = container_of(interval->to, struct nft_rbtree_elem, ext);
>> } else {
>> --
>> 2.47.3
>
>
> Can you test this fix instead? Thanks
Hello Pablo,
Thanks for this improved fix. I replayed the reproducer I had that
triggers the
bug on the kernel that includes your patch, and I confirm that it fixes
the UAF.
Let me know if I could be of further assistance.
Regards,
Jérémy
next prev parent reply other threads:[~2026-10-06 13:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-05 20:04 Jérémy Jean
2026-10-05 21:20 ` Pablo Neira Ayuso
2026-10-05 21:42 ` Pablo Neira Ayuso
2026-10-05 23:05 ` Pablo Neira Ayuso
2026-10-06 13:17 ` Jérémy Jean [this message]
2026-10-07 22:19 ` 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=9a9f2587b7bd37c8d03d0105cf968b25@oss.cyber.gouv.fr \
--to=jeremy.jean@oss.cyber.gouv.fr \
--cc=coreteam@netfilter.org \
--cc=fw@strlen.de \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®