From: Florian Westphal <fw@strlen.de>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH nf 4/4] netfilter: nf_conntrack: fix crash due to removal of uninitialised entry
Date: Wed, 16 Jul 2025 17:59:41 +0200 [thread overview]
Message-ID: <aHfMbT1txNXpdK_7@strlen.de> (raw)
In-Reply-To: <aHbRhj-NW3frJt0v@calendula>
Pablo Neira Ayuso <pablo@netfilter.org> wrote:
> On Mon, Jul 14, 2025 at 04:36:35PM +0200, Florian Westphal wrote:
> > Pablo Neira Ayuso <pablo@netfilter.org> wrote:
> > > On Thu, Jul 03, 2025 at 04:21:51PM +0200, Florian Westphal wrote:
> > > > Pablo Neira Ayuso <pablo@netfilter.org> wrote:
> > > > > Thanks for the description, this scenario is esoteric.
> > > > >
> > > > > Is this bug fully reproducible?
> > > >
> > > > No. Unicorn. Only happened once.
> > > > Everything is based off reading the backtrace and vmcore.
> > >
> > > I guess this needs a chaos money to trigger this bug. Else, can we try to catch this unicorn again?
> >
> > I would not hold my breath. But I don't see anything that prevents the
> > race described in 4/4, and all the things match in the vmcore, including
> > increment of clash resolution counter. If you think its too perfect
> > then ok, we can keep 4/4 back until someone else reports this problem
> > again.
>
> Hm, I think your sequence is possible, it is the SLAB_TYPESAFE_BY_RCU rule
> that allows for this to occur.
>
> Could this rare sequence still happen?
>
> cpu x cpu y cpu z
> found entry E found entry E
> E is expired <preemption>
> nf_ct_delete()
> return E to rcu slab
> init_conntrack
> <preemption> NOTE: ct->status not yet set to zero
>
> cpu y resumes, it observes E as expired but CONFIRMED:
> <resumes>
> nf_ct_expired()
> -> yes (ct->timeout is 30s)
> confirmed bit set.
Yes, that can happen, but then the refcount can't be incremented
as its 0 (-> entry is skipped). If its nonzero but the object was returned
by the kmem cache we have a different kind of bug (free with refcount > 0),
or use-after-free.
next prev parent reply other threads:[~2025-07-16 15:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-27 14:27 [PATCH nf 0/4] netfilter: conntrack: fix obscure confirmed race Florian Westphal
2025-06-27 14:27 ` [PATCH nf 1/4] selftests: netfilter: conntrack_resize.sh: extend resize test Florian Westphal
2025-06-27 14:27 ` [PATCH nf 2/4] selftests: netfilter: add conntrack clash resolution test case Florian Westphal
2025-06-27 14:27 ` [PATCH nf 3/4] selftests: netfilter: conntrack_resize.sh: also use udpclash tool Florian Westphal
2025-06-27 14:27 ` [PATCH nf 4/4] netfilter: nf_conntrack: fix crash due to removal of uninitialised entry Florian Westphal
2025-07-03 13:56 ` Pablo Neira Ayuso
2025-07-03 14:21 ` Florian Westphal
2025-07-14 13:51 ` Pablo Neira Ayuso
2025-07-14 14:36 ` Florian Westphal
2025-07-15 22:09 ` Pablo Neira Ayuso
2025-07-16 15:59 ` Florian Westphal [this message]
2025-07-16 17:00 ` Pablo Neira Ayuso
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=aHfMbT1txNXpdK_7@strlen.de \
--to=fw@strlen.de \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.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.