From: Greg KH <gregkh@linuxfoundation.org>
To: "Ömer Mete Kaya" <omermetekaya0@gmail.com>
Cc: rafael@kernel.org, dakr@kernel.org, akpm@linux-foundation.org,
edumazet@google.com, brauner@kernel.org,
driver-core@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kobject: fix use-after-free in tagged uevent broadcast
Date: Sun, 22 Nov 2026 10:41:58 +0100 [thread overview]
Message-ID: <2026112237-delegate-neon-7b4c@gregkh> (raw)
In-Reply-To: <20261122061751.178540-1-omermetekaya0@gmail.com>
On Sun, Nov 22, 2026 at 09:17:46AM +0300, Ömer Mete Kaya wrote:
> kobject_uevent_net_broadcast() accesses net->uevent_sock->sk without
> protection in the tagged (namespace-aware) path. During network namespace
> teardown, uevent_net_exit() frees the uevent_sock while a concurrent
> kobject_uevent_env() call can still reference it, causing a
> use-after-free.
>
> Extend uevent_sock_mutex to cover the tagged broadcast path and the
> netlink receive path, serializing them with teardown: in
> uevent_net_exit(), set net->uevent_sock to NULL under the mutex before
> releasing the socket. In the tagged broadcast path and in
> uevent_net_rcv_skb(), check for NULL under the same mutex before
> accessing the socket.
>
> Discovered by Sashiko, not triggered, not runtime tested.
Please test and get a reproducer before attempting such a change.
thanks,
greg k-h
prev parent reply other threads:[~2026-11-22 9:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-22 6:17 [PATCH] kobject: fix use-after-free in tagged uevent broadcast Ömer Mete Kaya
2026-11-22 9:41 ` Greg KH [this message]
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=2026112237-delegate-neon-7b4c@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=brauner@kernel.org \
--cc=dakr@kernel.org \
--cc=driver-core@lists.linux.dev \
--cc=edumazet@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=omermetekaya0@gmail.com \
--cc=rafael@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