linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: syzbot <syzbot+0b0095300dfeb8a83dc8@syzkaller.appspotmail.com>
To: andreyknvl@google.com, laurent.pinchart@ideasonboard.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: Tue, 10 Oct 2023 14:11:35 -0700	[thread overview]
Message-ID: <000000000000dc11d106076326fe@google.com> (raw)
In-Reply-To: <0000000000003ee3610599d20096@google.com>

This bug is marked as fixed by commit:
media: uvcvideo: Avoid cyclic entity chains due to malformed USB descriptors

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=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

  parent reply	other threads:[~2023-10-10 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
2023-07-20 11:54     ` Aleksandr Nogikh
2023-10-10 21:11 ` syzbot [this message]
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=000000000000dc11d106076326fe@google.com \
    --to=syzbot+0b0095300dfeb8a83dc8@syzkaller.appspotmail.com \
    --cc=andreyknvl@google.com \
    --cc=laurent.pinchart@ideasonboard.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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).