From: Greg KH <gregkh@linuxfoundation.org>
To: Fahad Alharbi <fahad@codepure.com>
Cc: stable@vger.kernel.org, security@kernel.org, security@ubuntu.com,
Sasha Levin <sashal@kernel.org>, Florian Westphal <fw@strlen.de>,
Pablo Neira Ayuso <pablo@netfilter.org>,
Jozsef Kadlecsik <kadlec@netfilter.org>,
netfilter-devel@vger.kernel.org, coreteam@netfilter.org,
netdev@vger.kernel.org
Subject: Re: nft_set_pipapo: UAF and double free from a stranded GC batch in the 5.15.y / 6.1.y / 6.6.y backports of 9df95785d3d8
Date: Tue, 4 Aug 2026 08:01:12 +0200 [thread overview]
Message-ID: <2026080436-dyslexic-willfully-fb2e@gregkh> (raw)
In-Reply-To: <CACiD-V2ymG+0DA2aLwHWeH7oejy0g=n1NUZ6Ce9NXvJFhwJP4Q@mail.gmail.com>
On Mon, Aug 03, 2026 at 09:19:28PM +0300, Fahad Alharbi wrote:
> Hello,
>
> 6.6.148 backported the pipapo on-demand-clone series, but two commits from
> the original 2024 series were not included. Two consequences are visible in
> the source. Both are straightforward to confirm; no reproducer is needed.
>
> Requested trees: 6.6.y
>
> Missing commits:
>
> 8b8a2417558c ("netfilter: nft_set_pipapo: prepare destroy function for
> on-demand clone")
> 532aec7e878b ("netfilter: nft_set_pipapo: remove dirty flag")
>
> Both are Florian Westphal, 2024-04-25, and both are present in 6.10.y
> through 7.1.y and in mainline. Neither is in 6.6.y.
That is because they do not cleanly apply there. Can you provide
working backports for that tree, and any other older tree that you think
needs it, so we can queue them up?
thanks,
greg k-h
next parent reply other threads:[~2026-08-04 6:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CACiD-V1TcRTcQotj-15KvpSr8hG26y6PDx=WU5MVAdHMEsgopA@mail.gmail.com>
[not found] ` <2026080355-catcher-absurd-f9e2@gregkh>
[not found] ` <CACiD-V2ymG+0DA2aLwHWeH7oejy0g=n1NUZ6Ce9NXvJFhwJP4Q@mail.gmail.com>
2026-08-04 6:01 ` Greg KH [this message]
2026-08-05 16:41 ` nft_set_pipapo: UAF and double free from a stranded GC batch in the 5.15.y / 6.1.y / 6.6.y backports of 9df95785d3d8 Sasha Levin
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=2026080436-dyslexic-willfully-fb2e@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=coreteam@netfilter.org \
--cc=fahad@codepure.com \
--cc=fw@strlen.de \
--cc=kadlec@netfilter.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=sashal@kernel.org \
--cc=security@kernel.org \
--cc=security@ubuntu.com \
--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