public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Pablo Neira Ayuso <pablo@netfilter.org>
To: netfilter-devel@vger.kernel.org
Cc: fw@strlen.de, gregkh@linuxfoundation.org, sashal@kernel.org,
	stable@vger.kernel.org
Subject: [PATCH netfilter -stable,4.14 0/6] stable fixes for 4.14
Date: Thu, 11 May 2023 17:41:37 +0200	[thread overview]
Message-ID: <20230511154143.52469-1-pablo@netfilter.org> (raw)

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.

The following list shows the backported patches, I am using original commit IDs
for reference:

1) cd5125d8f518 ("netfilter: nf_tables: split set destruction in deactivate and destroy phase")

2) f6ac85858976 ("netfilter: nf_tables: unbind set in rule from commit path")

3) 7f4dae2d7f03 ("netfilter: nft_hash: fix nft_hash_deactivate")

4) 6a0a8d10a366 ("netfilter: nf_tables: use-after-free in failing rule with bound set")

5) 273fe3f1006e ("netfilter: nf_tables: bogus EBUSY when deleting set after flush")

6) c1592a89942e ("netfilter: nf_tables: deactivate anonymous set from preparation phase")

Please apply to 4.14-stable.

Thanks.

Florian Westphal (1):
  netfilter: nf_tables: split set destruction in deactivate and destroy phase

Pablo Neira Ayuso (5):
  netfilter: nf_tables: unbind set in rule from commit path
  netfilter: nft_hash: fix nft_hash_deactivate
  netfilter: nf_tables: use-after-free in failing rule with bound set
  netfilter: nf_tables: bogus EBUSY when deleting set after flush
  netfilter: nf_tables: deactivate anonymous set from preparation phase

 include/net/netfilter/nf_tables.h |  30 ++++++-
 net/netfilter/nf_tables_api.c     | 139 +++++++++++++++++++++---------
 net/netfilter/nft_dynset.c        |  22 ++++-
 net/netfilter/nft_immediate.c     |   6 +-
 net/netfilter/nft_lookup.c        |  21 ++++-
 net/netfilter/nft_objref.c        |  21 ++++-
 net/netfilter/nft_set_hash.c      |   2 +-
 7 files changed, 194 insertions(+), 47 deletions(-)

-- 
2.30.2


             reply	other threads:[~2023-05-11 15:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-11 15:41 Pablo Neira Ayuso [this message]
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 ` [PATCH netfilter -stable,4.14 0/6] stable fixes for 4.14 Sasha Levin
2023-05-13  3:25 ` 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=20230511154143.52469-1-pablo@netfilter.org \
    --to=pablo@netfilter.org \
    --cc=fw@strlen.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=sashal@kernel.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