All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+4af454407ec393de51d6@syzkaller.appspotmail.com>
To: aliceryhl@google.com, arve@android.com, brauner@kernel.org,
	 cmllamas@google.com, dualli@google.com,
	gregkh@linuxfoundation.org,  joel@joelfernandes.org,
	joelagnelf@nvidia.com, kernel-team@android.com,
	 linux-kernel@vger.kernel.org, maco@android.com,
	stable@vger.kernel.org,  surenb@google.com,
	syzkaller-bugs@googlegroups.com, tkjos@android.com
Subject: Re: [syzbot] [kernel?] KASAN: slab-use-after-free Write in binder_remove_device
Date: Sat, 24 May 2025 19:03:02 -0700	[thread overview]
Message-ID: <68327a56.a70a0220.29d4a0.07fc.GAE@google.com> (raw)
In-Reply-To: <6831b67f.a70a0220.253bc2.006f.GAE@google.com>

syzbot has bisected this issue to:

commit 12d909cac1e1c4147cc3417fee804ee12fc6b984
Author: Li Li <dualli@google.com>
Date:   Wed Dec 18 21:29:34 2024 +0000

    binderfs: add new binder devices to binder_devices

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=107228e8580000
start commit:   176e917e010c Add linux-next specific files for 20250523
git tree:       linux-next
final oops:     https://syzkaller.appspot.com/x/report.txt?x=127228e8580000
console output: https://syzkaller.appspot.com/x/log.txt?x=147228e8580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=e7902c752bef748
dashboard link: https://syzkaller.appspot.com/bug?extid=4af454407ec393de51d6
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=108b55f4580000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=1145e5f4580000

Reported-by: syzbot+4af454407ec393de51d6@syzkaller.appspotmail.com
Fixes: 12d909cac1e1 ("binderfs: add new binder devices to binder_devices")

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

      parent reply	other threads:[~2025-05-25  2:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-24 12:07 [syzbot] [kernel?] KASAN: slab-use-after-free Write in binder_remove_device syzbot
2025-05-24 17:40 ` Carlos Llamas
2025-05-24 20:01   ` syzbot
2025-05-25  2:03 ` 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=68327a56.a70a0220.29d4a0.07fc.GAE@google.com \
    --to=syzbot+4af454407ec393de51d6@syzkaller.appspotmail.com \
    --cc=aliceryhl@google.com \
    --cc=arve@android.com \
    --cc=brauner@kernel.org \
    --cc=cmllamas@google.com \
    --cc=dualli@google.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=joel@joelfernandes.org \
    --cc=joelagnelf@nvidia.com \
    --cc=kernel-team@android.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maco@android.com \
    --cc=stable@vger.kernel.org \
    --cc=surenb@google.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=tkjos@android.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.