From: Sasha Levin <sashal@kernel.org>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: netfilter-devel@vger.kernel.org, fw@strlen.de,
gregkh@linuxfoundation.org, stable@vger.kernel.org
Subject: Re: [PATCH netfilter -stable,4.14 0/6] stable fixes for 4.14
Date: Thu, 11 May 2023 17:53:02 -0400 [thread overview]
Message-ID: <ZF1jvgyRpOjwhIJv@sashalap> (raw)
In-Reply-To: <20230511154143.52469-1-pablo@netfilter.org>
On Thu, May 11, 2023 at 05:41:37PM +0200, Pablo Neira Ayuso wrote:
>Hi Greg, Sasha,
>
>This is a backport of c1592a89942e ("netfilter: nf_tables: deactivate anonymous
>set from preparation phase") which fixes CVE-2023-32233. This patch requires
>dependency fixes which are not currently in the 4.14 branch.
Queued up, thanks!
--
Thanks,
Sasha
next prev parent reply other threads:[~2023-05-11 21:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-11 15:41 [PATCH netfilter -stable,4.14 0/6] stable fixes for 4.14 Pablo Neira Ayuso
2023-05-11 15:41 ` [PATCH -stable,4.14 1/6] netfilter: nf_tables: split set destruction in deactivate and destroy phase Pablo Neira Ayuso
2023-05-11 15:41 ` [PATCH -stable,4.14 2/6] netfilter: nf_tables: unbind set in rule from commit path Pablo Neira Ayuso
2023-05-11 15:41 ` [PATCH -stable,4.14 3/6] netfilter: nft_hash: fix nft_hash_deactivate Pablo Neira Ayuso
2023-05-11 15:41 ` [PATCH -stable,4.14 4/6] netfilter: nf_tables: use-after-free in failing rule with bound set Pablo Neira Ayuso
2023-05-11 15:41 ` [PATCH -stable,4.14 5/6] netfilter: nf_tables: bogus EBUSY when deleting set after flush Pablo Neira Ayuso
2023-05-11 15:41 ` [PATCH -stable,4.14 6/6] netfilter: nf_tables: deactivate anonymous set from preparation phase Pablo Neira Ayuso
2023-05-11 21:53 ` Sasha Levin [this message]
2023-05-13 3:25 ` [PATCH netfilter -stable,4.14 0/6] stable fixes for 4.14 luwei (O)
2023-05-13 6:20 ` Greg KH
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=ZF1jvgyRpOjwhIJv@sashalap \
--to=sashal@kernel.org \
--cc=fw@strlen.de \
--cc=gregkh@linuxfoundation.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
--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