All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+6c25f4750230faf70be9@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Forwarded: netdevsim: fix use-after-free in __nsim_dev_port_del
Date: Thu, 18 Jun 2026 00:40:17 -0700	[thread overview]
Message-ID: <6a33a0e1.d85dbdf7.1299fc.0007.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: 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

From b3aa94bf5977395e788b457e3bb073c2b7f4580d Mon Sep 17 00:00:00 2001
From: Hrushiraj Gandhi <hrushirajg23@gmail.com>
Date: Thu, 18 Jun 2026 13:03:56 +0530
Subject: [PATCH] netdevsim: fix use-after-free in __nsim_dev_port_del

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.

In __nsim_dev_port_del(), nsim_destroy() was called before
nsim_dev_port_debugfs_exit(), meaning free_netdev() freed the
netdevsim slab while debugfs files still held live pointers into it.
A concurrent reader with the file already open could pass
debugfs_file_get(), then dereference the freed pointer in
debugfs_u32_get(), triggering a slab-use-after-free.

Fix by calling nsim_dev_port_debugfs_exit() first, so
debugfs_remove_recursive() tears down the entire port ddir subtree
(invalidating all stale data pointers) before free_netdev() releases
the backing memory.

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/dev.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/net/netdevsim/dev.c b/drivers/net/netdevsim/dev.c
index f00fc2f9ebde..77417dd0f752 100644
--- a/drivers/net/netdevsim/dev.c
+++ b/drivers/net/netdevsim/dev.c
@@ -1544,8 +1544,8 @@ static void __nsim_dev_port_del(struct
nsim_dev_port *nsim_dev_port)
  list_del(&nsim_dev_port->list);
  if (nsim_dev_port_is_vf(nsim_dev_port))
  devl_rate_leaf_destroy(&nsim_dev_port->devlink_port);
- nsim_destroy(nsim_dev_port->ns);
  nsim_dev_port_debugfs_exit(nsim_dev_port);
+ nsim_destroy(nsim_dev_port->ns);
  if (nsim_dev_port_is_pf(nsim_dev_port))
  devl_port_resources_unregister(devlink_port);
  devl_port_unregister(devlink_port);
-- 
2.47.3

  reply	other threads:[~2026-06-18  7:40 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 ` syzbot [this message]
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
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=6a33a0e1.d85dbdf7.1299fc.0007.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.