From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: syzbot <syzbot+0b0095300dfeb8a83dc8@syzkaller.appspotmail.com>
Cc: andreyknvl@google.com, linux-kernel@vger.kernel.org,
linux-media@vger.kernel.org, linux-usb@vger.kernel.org,
mchehab@kernel.org, nogikh@google.com,
sakari.ailus@linux.intel.com, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] KASAN: use-after-free Read in __media_entity_remove_links
Date: Thu, 13 Jul 2023 00:11:12 +0300 [thread overview]
Message-ID: <20230712211112.GD30092@pendragon.ideasonboard.com> (raw)
In-Reply-To: <000000000000c26a66060035ad18@google.com>
On Tue, Jul 11, 2023 at 06:00:08AM -0700, syzbot wrote:
> This bug is marked as fixed by commit:
> media: uvcvideo: Avoid cyclic entity chains due to malformed
>
> 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: media: uvcvideo: Avoid cyclic entity chains due to malformed USB descriptors
Can a commit ID be used as well ?
> 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=0b0095300dfeb8a83dc8
>
> ---
> [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
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2023-07-12 21:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-16 13:15 KASAN: use-after-free Read in __media_entity_remove_links syzbot
2023-07-11 13:00 ` [syzbot] " syzbot
2023-07-12 21:11 ` Laurent Pinchart [this message]
2023-07-20 11:54 ` Aleksandr Nogikh
2023-10-10 21:11 ` syzbot
2023-10-24 21:11 ` syzbot
2023-11-07 21:12 ` syzbot
2023-11-21 21:13 ` syzbot
2023-11-21 21:45 ` Laurent Pinchart
2023-11-22 11:39 ` Aleksandr Nogikh
2023-12-06 11:40 ` syzbot
2023-12-20 11:41 ` syzbot
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=20230712211112.GD30092@pendragon.ideasonboard.com \
--to=laurent.pinchart@ideasonboard.com \
--cc=andreyknvl@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=nogikh@google.com \
--cc=sakari.ailus@linux.intel.com \
--cc=syzbot+0b0095300dfeb8a83dc8@syzkaller.appspotmail.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.