From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Sasha Levin <sashal@kernel.org>
Cc: Florian Westphal <fw@strlen.de>,
netfilter-devel@vger.kernel.org, stable@vger.kernel.org,
linux-kernel@vger.kernel.org, Ma Xinmeng <1564938642@qq.com>
Subject: Re: [PATCH 6.1 1/2] netfilter: nf_tables: allow to create netdev chain without device
Date: Fri, 2 Oct 2026 23:44:18 +0200 [thread overview]
Message-ID: <asAlssf9FAAFi4m_@chamomile> (raw)
In-Reply-To: <2026-10-02-1-daily-reply-0008-re-nf-tables-netdev-chain-6-1@kernel.org>
Hi,
On Fri, Oct 02, 2026 at 05:10:34PM -0400, Sasha Levin wrote:
> > This is a 6.1 backport of upstream commit 207296f1a03b; the hunk for
> > nft_delchain_hook() is dropped since that function is not present in 6.1.
>
> This series only brings in the prerequisites. The UAF fix itself isn't
> in it:
>
> fc0133428e7a ("netfilter: nf_tables: Tolerate chains with no remaining hooks")
> 375f222800bc ("netfilter: nf_tables: Simplify chain netdev notifier")
>
> 2/2 also adds b9703ed44ffb ("netfilter: nf_tables: support for adding
> new devices to an existing netdev chain") to 6.1 without the later
> fixes for it, none of which 6.1 has:
>
> 043d2acf5722 ("netfilter: nf_tables: drop module reference after updating chain")
> 7eaf837a4eb5 ("netfilter: nf_tables: Fix a memory leak in nf_tables_updchain")
> 1e1fb6f00f52 ("netfilter: nf_tables: reject table flag and netdev basechain updates")
> 216e7bf7402c ("netfilter: nf_tables: skip netdev hook unregistration if table is dormant")
> 688c15017d5c ("netfilter: nf_tables: don't unregister hook when table is dormant")
> 4ffcf5ca81c3 ("netfilter: nf_tables: use rcu chain hook list iterator from netlink dump path")
>
> It also needs the netdev chain parts of a6134e62dba2 ("netfilter:
> nf_tables: join hook list via splice_list_rcu() in commit phase") and
> cf5fb87fcdaa ("netfilter: nf_tables: reject duplicate device on
> updates"); 6.1 only has their flowtable parts. Without 043d2acf5722,
> every base chain update that carries a hook leaks a reference on the
> chain type module.
>
> Could you send a single 6.1 series in upstream order: the two
> prerequisites, the fixes above, then fc0133428e7a and 375f222800bc?
> Please start each patch with its "commit <sha> upstream." line and add
> a cover letter. An ack from Pablo or Florian would help too.
>
> 5.15 and 5.10 have the same UAF. Are you planning to cover them as well?
Yes, I am collecting backport patches and preparing a batch for you.
next prev parent reply other threads:[~2026-10-02 21:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-25 2:00 [PATCH request stable 6.12 6.6 6.1] netfilter: nf_tables_netdev_event UAF of binding chain Yu Junzhe
2026-09-25 5:07 ` Greg Kroah-Hartman
2026-09-25 7:51 ` Yu Junzhe
2026-09-25 7:51 ` [PATCH 6.12 1/2] netfilter: nf_tables: Tolerate chains with no remaining hooks Yu Junzhe
2026-09-25 7:51 ` [PATCH 6.12 2/2] netfilter: nf_tables: Simplify chain netdev notifier Yu Junzhe
2026-09-25 7:51 ` [PATCH 6.6 6.1 1/2] netfilter: nf_tables: Tolerate chains with no remaining hooks Yu Junzhe
2026-09-25 18:47 ` Sasha Levin
2026-10-01 3:51 ` [PATCH 6.1] netfilter: nf_tables: fix UAF in nf_tables_netdev_event walker Ma Xinmeng
2026-10-01 8:46 ` Pablo Neira Ayuso
2026-10-02 4:25 ` [PATCH 6.1 1/2] netfilter: nf_tables: allow to create netdev chain without device Ma Xinmeng
2026-10-02 21:10 ` Sasha Levin
2026-10-02 21:44 ` Pablo Neira Ayuso [this message]
[not found] ` <20261002042509.711-1-1564938642@qq.com>
2026-10-02 4:25 ` [PATCH 6.1 2/2] netfilter: nf_tables: support for adding new devices to an existing netdev chain Ma Xinmeng
2026-09-25 7:51 ` [PATCH 6.6 6.1 2/2] netfilter: nf_tables: Simplify chain netdev notifier Yu Junzhe
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=asAlssf9FAAFi4m_@chamomile \
--to=pablo@netfilter.org \
--cc=1564938642@qq.com \
--cc=fw@strlen.de \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.