From: syzbot <syzbot+6c25f4750230faf70be9@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Forwarded: [PATCH] netdevsim: fix use-after-free in __nsim_dev_port_del
Date: Thu, 18 Jun 2026 05:34:35 -0700 [thread overview]
Message-ID: <6a33e5db.537e895e.3cc275.0000.GAE@google.com> (raw)
In-Reply-To: <6a32e8e7.9e4c924b.10726f.0023.GAE@google.com>
For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.
***
Subject: [PATCH] netdevsim: fix use-after-free in __nsim_dev_port_del
Author: hrushirajg23@gmail.com
#syz test: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
debugfs files created under a port's ddir (ethtool/get_err,
ethtool/set_err, ring params, bpf_offloaded_id, udp_ports/inject_error,
etc.) store raw pointers directly into the netdevsim struct, which lives
in the net_device private data kmalloc slab.
If these files outlive the netdevsim struct, a concurrent reader can
trigger a slab-use-after-free by passing debugfs_file_get() (which only
checks dentry lifetime) and then dereferencing the freed data pointer
in debugfs_u32_get().
In __nsim_dev_port_del(), nsim_destroy() is called before
nsim_dev_port_debugfs_exit(). However, nsim_destroy() calls free_netdev()
at its end, while nsim_dev_port_debugfs_exit() removes the port's
debugfs directory. This means the slab is freed before the debugfs
files are removed.
Fix by calling debugfs_remove_recursive(ns->nsim_dev_port->ddir) in
nsim_destroy() right before free_netdev(). This ensures all per-port
debugfs files are destroyed synchronously before the backing memory is
freed. The subsequent call to nsim_dev_port_debugfs_exit() in
__nsim_dev_port_del() becomes a harmless no-op.
Reported-by: syzbot+6c25f4750230faf70be9@syzkaller.appspotmail.com
Closes: https://syzkaller.appspot.com/bug?extid=6c25f4750230faf70be9
Fixes: e05b2d141fef ("netdevsim: move netdev creation/destruction to dev probe")
Signed-off-by: Hrushiraj Gandhi <hrushirajg23@gmail.com>
---
drivers/net/netdevsim/netdev.c | 16 ++++++++++++++++
1 file changed, 16 insertions(+)
diff --git a/drivers/net/netdevsim/netdev.c b/drivers/net/netdevsim/netdev.c
index a750768912b5..511139d65d69 100644
--- a/drivers/net/netdevsim/netdev.c
+++ b/drivers/net/netdevsim/netdev.c
@@ -1213,6 +1213,22 @@ void nsim_destroy(struct netdevsim *ns)
ns->page = NULL;
}
+ /*
+ * Remove all per-port debugfs files before free_netdev() releases
+ * the netdevsim struct. Files like ethtool/get_err, bpf_offloaded_id,
+ * etc. store raw pointers into ns (netdev_priv data inside the
+ * net_device slab). A concurrent reader with the file open could pass
+ * debugfs_file_get() and then dereference freed memory if these files
+ * outlive free_netdev(). debugfs_remove_recursive() on the parent ddir
+ * handles this atomically; the subsequent nsim_dev_port_debugfs_exit()
+ * call in __nsim_dev_port_del() becomes a harmless no-op.
+ *
+ * The three explicitly tracked dentries (vlan_dfs, qr_dfs, pp_dfs)
+ * are children of ddir and are covered by the recursive removal below,
+ * so their individual debugfs_remove() calls become no-ops too.
+ */
+ debugfs_remove_recursive(ns->nsim_dev_port->ddir);
+
free_netdev(dev);
}
--
2.47.3
next prev parent reply other threads:[~2026-06-18 12:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-17 18:35 [syzbot] [fs?] KASAN: slab-use-after-free Read in debugfs_u32_get (2) syzbot
2026-06-18 7:40 ` Forwarded: netdevsim: fix use-after-free in __nsim_dev_port_del syzbot
2026-06-18 8:51 ` Forwarded: Re: [syzbot] netdevsim fix syzbot
2026-06-18 9:01 ` Forwarded: [PATCH] netdevsim: fix use-after-free in __nsim_dev_port_del syzbot
2026-06-18 12:34 ` syzbot [this message]
2026-06-18 13:12 ` syzbot
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=6a33e5db.537e895e.3cc275.0000.GAE@google.com \
--to=syzbot+6c25f4750230faf70be9@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.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 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.