From: Carlos Llamas <cmllamas@google.com>
To: syzbot <syzbot+9ba7a8cdae0440edd57b@syzkaller.appspotmail.com>
Cc: aardelean@baylibre.com, aliceryhl@google.com, arve@android.com,
brauner@kernel.org, gregkh@linuxfoundation.org, hdanton@sina.com,
joel@joelfernandes.org, jonathan.cameron@huawei.com,
linux-kernel@vger.kernel.org, maco@android.com,
nuno.sa@analog.com, surenb@google.com,
syzkaller-bugs@googlegroups.com, tkjos@android.com
Subject: Re: [syzbot] [kernel?] KASAN: slab-use-after-free Read in binder_release_work
Date: Mon, 13 Jan 2025 14:53:15 +0000 [thread overview]
Message-ID: <Z4Uo20hujg8JQN3f@google.com> (raw)
In-Reply-To: <6782f470.050a0220.216c54.0027.GAE@google.com>
On Sat, Jan 11, 2025 at 02:45:04PM -0800, syzbot wrote:
> syzbot suspects this issue was fixed by commit:
>
> commit 7e20434cbca814cb91a0a261ca0106815ef48e5f
> Author: Carlos Llamas <cmllamas@google.com>
> Date: Thu Sep 26 23:36:14 2024 +0000
>
> binder: fix freeze UAF in binder_release_work()
>
> bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1380f218580000
> start commit: 3e5e6c9900c3 Merge tag 'nfsd-6.12-3' of git://git.kernel.o..
> git tree: upstream
> kernel config: https://syzkaller.appspot.com/x/.config?x=cf5329baa0b5a257
> dashboard link: https://syzkaller.appspot.com/bug?extid=9ba7a8cdae0440edd57b
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1245faa7980000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=105db630580000
>
> If the result looks correct, please mark the issue as fixed by replying with:
>
> #syz fix: binder: fix freeze UAF in binder_release_work()
>
> For information about bisection process see: https://goo.gl/tpsmEJ#bisection
#syz fix: binder: fix freeze UAF in binder_release_work()
prev parent reply other threads:[~2025-01-13 14:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-02 21:10 [syzbot] [kernel?] KASAN: slab-use-after-free Read in binder_release_work syzbot
2024-10-03 0:59 ` Hillf Danton
2024-10-03 1:20 ` syzbot
2025-01-11 22:45 ` syzbot
2025-01-13 14:53 ` Carlos Llamas [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=Z4Uo20hujg8JQN3f@google.com \
--to=cmllamas@google.com \
--cc=aardelean@baylibre.com \
--cc=aliceryhl@google.com \
--cc=arve@android.com \
--cc=brauner@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=hdanton@sina.com \
--cc=joel@joelfernandes.org \
--cc=jonathan.cameron@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maco@android.com \
--cc=nuno.sa@analog.com \
--cc=surenb@google.com \
--cc=syzbot+9ba7a8cdae0440edd57b@syzkaller.appspotmail.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.