[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <000000000000dd5c040600366c6f@google.com>
Date: Tue, 11 Jul 2023 06:53:34 -0700
From: syzbot <syzbot+07bb74aeafc88ba7d5b4@...kaller.appspotmail.com>
To: bst@...gutronix.de, dania@...onnect-ltd.com, davem@...emloft.net,
dev.kurt@...dijck-laurijssen.be, ecathinds@...il.com,
kernel@...gutronix.de, linux-can@...r.kernel.org,
linux-kernel@...r.kernel.org, linux@...pel-privat.de,
lkp@...el.com, maxime.jayat@...ile-devices.fr, mkl@...gutronix.de,
netdev@...r.kernel.org, nogikh@...gle.com, o.rempel@...gutronix.de,
robin@...tonic.nl, socketcan@...tkopp.net,
syzkaller-bugs@...glegroups.com
Subject: Re: [syzbot] KASAN: use-after-free Write in j1939_sock_pending_del
This bug is marked as fixed by commit:
can: j1939: socket: rework socket locking for
But I can't find it in the tested trees[1] for more than 90 days.
Is it a correct commit? Please update it by replying:
#syz fix: exact-commit-title
Until then the bug is still considered open and new crashes with
the same signature are ignored.
Kernel: Linux
Dashboard link: https://syzkaller.appspot.com/bug?extid=07bb74aeafc88ba7d5b4
---
[1] I expect the commit to be present in:
1. for-kernelci branch of
git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git
2. master branch of
git://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git
3. master branch of
git://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf.git
4. main branch of
git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git
The full list of 9 trees can be found at
https://syzkaller.appspot.com/upstream/repos
Powered by blists - more mailing lists