From: syzbot <syzbot+810b8555076779a07399@syzkaller.appspotmail.com>
To: cmllamas@google.com
Cc: arve@android.com, brauner@kernel.org, cmllamas@google.com,
gregkh@linuxfoundation.org, joel@joelfernandes.org,
linux-kernel@vger.kernel.org, maco@android.com,
surenb@google.com, syzkaller-bugs@googlegroups.com,
tkjos@android.com
Subject: Re: [syzbot] [kernel?] KASAN: slab-use-after-free Write in binder_add_device
Date: Mon, 24 Mar 2025 17:59:47 -0700 [thread overview]
Message-ID: <67e20003.050a0220.a7ebc.0034.GAE@google.com> (raw)
In-Reply-To: <Z-H__dbcSB4htqUZ@google.com>
> On Mon, Mar 24, 2025 at 05:49:53PM -0700, syzbot wrote:
>> > On Sun, Mar 16, 2025 at 03:51:27PM -0700, syzbot wrote:
>> >> Hello,
>> >>
>> >> syzbot found the following issue on:
>> >>
>> >> HEAD commit: b7f94fcf5546 Merge tag 'sched_ext-for-6.14-rc6-fixes' of g..
>> >> git tree: upstream
>> >> console output: https://syzkaller.appspot.com/x/log.txt?x=134f303f980000
>> >> kernel config: https://syzkaller.appspot.com/x/.config?x=cdc24cb631dc9bc4
>> >> dashboard link: https://syzkaller.appspot.com/bug?extid=810b8555076779a07399
>> >> compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
>> >
>> > #syz test
>>
>> This crash does not have a reproducer. I cannot test it.
>
> This is likely another version of this report:
> https://syzkaller.appspot.com/bug?extid=353d7b75658a95aa955a
> where access to the binder_devices list is unprotected.
>
> #syz dup: slab-use-after-free Write in binderfs_evict_inode
can't find the dup bug
next prev parent reply other threads:[~2025-03-25 0:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-16 22:51 [syzbot] [kernel?] KASAN: slab-use-after-free Write in binder_add_device syzbot
2025-03-17 3:38 ` Aleksandr Nogikh
2025-03-17 3:38 ` syzbot
2025-03-25 0:49 ` Carlos Llamas
2025-03-25 0:49 ` syzbot
2025-03-25 0:59 ` Carlos Llamas
2025-03-25 0:59 ` syzbot [this message]
2025-03-25 1:03 ` Carlos Llamas
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=67e20003.050a0220.a7ebc.0034.GAE@google.com \
--to=syzbot+810b8555076779a07399@syzkaller.appspotmail.com \
--cc=arve@android.com \
--cc=brauner@kernel.org \
--cc=cmllamas@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=joel@joelfernandes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maco@android.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox