From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>
Cc: Willy Tarreau <w@1wt.eu>, n3rd <18670333770@163.com>,
"netfilter-devel@vger.kernel.org"
<netfilter-devel@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Florian Westphal <fw@strlen.de>,
"security@kernel.org" <security@kernel.org>
Subject: Re: [SECURITY] netfilter: ipset: double free in hash resize vs inline gc
Date: Fri, 20 Nov 2026 10:59:58 +0100 [thread overview]
Message-ID: <awAaHlAKHEMyiVi8@chamomile> (raw)
In-Reply-To: <3a321704-59ad-7756-102c-a5c6ae77be88@blackhole.kfki.hu>
Hi,
On Fri, Nov 20, 2026 at 09:28:02AM +0100, Jozsef Kadlecsik wrote:
> Hi,
>
> On Fri, 20 Nov 2026, Willy Tarreau wrote:
[..]
> > Can you please propose patches for your different reports ? This is generally
> > trivial to do for LLMs after they find a bug because they have a complete
> > view of the problem.
>
> The current custom hash implementation backend suffers major internal issues
> which cannot properly be solved without a complete redesign.
>
> Florian worked really hard and rewroted the custom hash implementation with
> an rhashtable based one which fixes the issue in question and other issues
> lurking in the current ipset code as well, without loosing any
> functionality.
>
> It is heading into nf-next and at the end going to be backported to the
> stable branches too. Thus all known/reported ipset related issues will be
> fixed in "one step".
This is all coming in the next nf-next.git PR for this week, I'm
working on this.
prev parent reply other threads:[~2026-11-20 10:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3a7a0984.dc22e.1a1f6bb0630.Coremail.18670333770@163.com>
2026-11-20 5:37 ` [SECURITY] netfilter: ipset: double free in hash resize vs inline gc Willy Tarreau
2026-11-20 8:28 ` Jozsef Kadlecsik
2026-11-20 9:59 ` Pablo Neira Ayuso [this message]
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=awAaHlAKHEMyiVi8@chamomile \
--to=pablo@netfilter.org \
--cc=18670333770@163.com \
--cc=fw@strlen.de \
--cc=kadlec@blackhole.kfki.hu \
--cc=linux-kernel@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=security@kernel.org \
--cc=w@1wt.eu \
/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