From: Adarsh Das <adarshdas950@gmail.com>
To: gregkh@linuxfoundation.org
Cc: adarshdas950@gmail.com, dakr@kernel.org,
driver-core@lists.linux.dev, linux-kernel@vger.kernel.org,
rafael@kernel.org, stable@vger.kernel.org,
syzbot+4393dfdddf166f2de2b0@syzkaller.appspotmail.com
Subject: [PATCH v4] kobject: fix uevent socket use-after-free on net namespace delete
Date: Fri, 18 Sep 2026 15:13:36 +0530 [thread overview]
Message-ID: <20260918094336.6096-1-adarshdas950@gmail.com> (raw)
In-Reply-To: <2026091807-coma-unraveled-a65f@gregkh>
When a network namespace is deleted, we free its uevent socket. But
sometimes a device in that namespace is still being removed and tries to
send a uevent through that socket. The socket is already freed, so KASAN
reports a use-after-free.
Take a lock around both the send path and the free path, and clear the
pointer before freeing so nobody uses it after free.
Reported-and-tested-by: syzbot+4393dfdddf166f2de2b0@syzkaller.appspotmail.com
Tested-by: Adarsh Das <adarshdas950@gmail.com>
Assisted-by: LLM
Link: https://lore.kernel.org/all/20260917144206.85836-1-adarshdas950@gmail.com/
Signed-off-by: Adarsh Das <adarshdas950@gmail.com>
---
v4:
- Use scoped_guard(mutex) instead of block in uevent_net_exit
v3:
- Use guard(mutex) per review
v2:
- Add Assisted-by and Tested-by tags per review
lib/kobject_uevent.c | 26 ++++++++++++++++++--------
1 file changed, 18 insertions(+), 8 deletions(-)
diff --git a/lib/kobject_uevent.c b/lib/kobject_uevent.c
index ddbc4d7482d2..14e2e15d4ea7 100644
--- a/lib/kobject_uevent.c
+++ b/lib/kobject_uevent.c
@@ -13,6 +13,7 @@
* Greg Kroah-Hartman <greg@kroah.com>
*/
+#include <linux/cleanup.h>
#include <linux/spinlock.h>
#include <linux/string.h>
#include <linux/kobject.h>
@@ -411,9 +412,14 @@ static int kobject_uevent_net_broadcast(struct kobject *kobj,
devpath);
else {
const struct net *net = container_of(ns, struct net, ns);
-
- ret = uevent_net_broadcast_tagged(net->uevent_sock->sk, env,
- action_string, devpath);
+ struct uevent_sock *ue_sk;
+
+ guard(mutex)(&uevent_sock_mutex);
+ ue_sk = net->uevent_sock;
+ if (ue_sk && ue_sk->sk)
+ ret = uevent_net_broadcast_tagged(ue_sk->sk, env,
+ action_string,
+ devpath);
}
#endif
@@ -804,14 +810,18 @@ static int uevent_net_init(struct net *net)
static void uevent_net_exit(struct net *net)
{
- struct uevent_sock *ue_sk = net->uevent_sock;
+ struct uevent_sock *ue_sk;
- if (sock_net(ue_sk->sk)->user_ns == &init_user_ns) {
- mutex_lock(&uevent_sock_mutex);
- list_del(&ue_sk->list);
- mutex_unlock(&uevent_sock_mutex);
+ scoped_guard(mutex, &uevent_sock_mutex) {
+ ue_sk = net->uevent_sock;
+ net->uevent_sock = NULL;
+ if (ue_sk && sock_net(ue_sk->sk)->user_ns == &init_user_ns)
+ list_del(&ue_sk->list);
}
+ if (!ue_sk)
+ return;
+
netlink_kernel_release(ue_sk->sk);
kfree(ue_sk);
}
--
2.55.0
prev parent reply other threads:[~2026-09-18 9:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-17 14:42 [PATCH] " Adarsh Das
2026-09-17 14:51 ` Greg KH
2026-09-17 15:18 ` Adarsh Das
2026-09-17 15:21 ` Greg KH
2026-09-17 17:08 ` [PATCH v2] " Adarsh Das
2026-09-17 17:08 ` Adarsh Das
2026-09-17 17:40 ` Greg KH
2026-09-18 6:08 ` [PATCH v3] " Adarsh Das
2026-09-18 8:14 ` Greg KH
2026-09-18 8:14 ` Greg KH
2026-09-18 9:43 ` Adarsh Das [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=20260918094336.6096-1-adarshdas950@gmail.com \
--to=adarshdas950@gmail.com \
--cc=dakr@kernel.org \
--cc=driver-core@lists.linux.dev \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=stable@vger.kernel.org \
--cc=syzbot+4393dfdddf166f2de2b0@syzkaller.appspotmail.com \
/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
all inboxes | Powered by JetHome®