All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+e8651419c44dbc2b8768@syzkaller.appspotmail.com>
To: davem@davemloft.net, edumazet@google.com, horms@kernel.org,
	 johan.hedberg@gmail.com, kuba@kernel.org,
	linux-bluetooth@vger.kernel.org,  linux-kernel@vger.kernel.org,
	luiz.dentz@gmail.com, luiz.von.dentz@intel.com,
	 marcel@holtmann.org, netdev@vger.kernel.org, pabeni@redhat.com,
	 syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [bluetooth?] possible deadlock in mgmt_remove_adv_monitor_complete
Date: Tue, 17 Jun 2025 10:36:03 -0700	[thread overview]
Message-ID: <6851a783.050a0220.2608ac.001f.GAE@google.com> (raw)
In-Reply-To: <0000000000004fc49a0617826da3@google.com>

syzbot suspects this issue was fixed by commit:

commit e6ed54e86aae9e4f7286ce8d5c73780f91b48d1c
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date:   Tue Jun 3 20:12:39 2025 +0000

    Bluetooth: MGMT: Fix UAF on mgmt_remove_adv_monitor_complete

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=177d790c580000
start commit:   4c49f38e20a5 net: stmmac: fix TSO DMA API usage causing oops
git tree:       net
kernel config:  https://syzkaller.appspot.com/x/.config?x=1362a5aee630ff34
dashboard link: https://syzkaller.appspot.com/bug?extid=e8651419c44dbc2b8768
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=11348b30580000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=17abf40f980000

If the result looks correct, please mark the issue as fixed by replying with:

#syz fix: Bluetooth: MGMT: Fix UAF on mgmt_remove_adv_monitor_complete

For information about bisection process see: https://goo.gl/tpsmEJ#bisection

      parent reply	other threads:[~2025-06-17 17:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-03  1:13 [syzbot] [bluetooth?] possible deadlock in mgmt_remove_adv_monitor_complete syzbot
2024-12-01 19:35 ` syzbot
2025-06-17 17:36 ` syzbot [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=6851a783.050a0220.2608ac.001f.GAE@google.com \
    --to=syzbot+e8651419c44dbc2b8768@syzkaller.appspotmail.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=johan.hedberg@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    --cc=luiz.von.dentz@intel.com \
    --cc=marcel@holtmann.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --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.