From: Daehyeon Ko <4ncienth@gmail.com>
To: fw@strlen.de
Cc: pablo@netfilter.org, phil@nwl.cc,
netfilter-devel@vger.kernel.org, coreteam@netfilter.org,
netdev@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH net] netfilter: conntrack: avoid recursive master destruction
Date: Fri, 2 Oct 2026 14:39:41 +0900 [thread overview]
Message-ID: <20261002053941.1132097-1-4ncienth@gmail.com> (raw)
In-Reply-To: <ar6yM0h2zdVUU4rt@strlen.de>
Thanks for taking a look.
I think this check is reasonable for CTA_TUPLE_MASTER, but it does not seem
to make master chains impossible by itself. There is another master writer
in init_conntrack(): expectation fulfillment assigns exp->master to the new
conntrack.
In particular, ctnetlink_glue_attach_expect() can attach an expectation
from an NFQUEUE verdict and set assign_helper. The expected child then has
both a master and a helper, so it can serve as the master of another
userspace-helper expectation. That path does not pass through the proposed
check and has no cumulative depth bound.
This helper propagation was intentionally restored by dcb0f9aefdd6
("netfilter: nf_conntrack_expect: restore helper propagation via
expectation") for SIP, H.323 and userspace helpers. Restricting all nested
masters would therefore need a wider helper/expectation compatibility
change.
For that reason I think nf_ct_destroy() still needs to be stack-safe. The
creation-time check could be added separately if nested conntrackd restore
should also be rejected. Does that match your intended invariant?
Thanks,
Daehyeon
next prev parent reply other threads:[~2026-10-02 5:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-01 18:02 [PATCH net] netfilter: conntrack: avoid recursive master destruction Daehyeon Ko
2026-10-01 19:19 ` Florian Westphal
2026-10-02 5:39 ` Daehyeon Ko [this message]
2026-10-02 9:56 ` Pablo Neira Ayuso
2026-10-02 9:55 ` Pablo Neira Ayuso
2026-10-02 9:55 ` Pablo Neira Ayuso
2026-10-02 16:56 ` [PATCH v2 net] netfilter: conntrack: reject nested ctnetlink master chains Daehyeon Ko
2026-10-02 16:58 ` netdev-bot+sinfo
2026-10-02 17:35 ` Florian Westphal
2026-10-06 7:57 ` netdev-bot+sashiko
2026-10-07 1:33 ` Daehyeon Ko
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=20261002053941.1132097-1-4ncienth@gmail.com \
--to=4ncienth@gmail.com \
--cc=coreteam@netfilter.org \
--cc=fw@strlen.de \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=phil@nwl.cc \
--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