From: syzbot <syzbot+99d6c66dbbc484f50e1c@syzkaller.appspotmail.com>
To: gregkh@linuxfoundation.org, hdanton@sina.com,
linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
linux-usb@vger.kernel.org, mchehab@kernel.org,
paskripkin@gmail.com, stern@rowland.harvard.edu,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [usb?] [media?] KASAN: use-after-free Read in em28xx_init_extension (2)
Date: Tue, 13 May 2025 08:02:01 -0700 [thread overview]
Message-ID: <68235ee9.050a0220.f2294.09fc.GAE@google.com> (raw)
In-Reply-To: <000000000000453f3d05db72fc7e@google.com>
syzbot has bisected this issue to:
commit a368ecde8a5055b627749b09c6218ef793043e47
Author: Alan Stern <stern@rowland.harvard.edu>
Date: Thu Jun 27 19:56:18 2024 +0000
USB: core: Fix duplicate endpoint bug by clearing reserved bits in the descriptor
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=12cf6cd4580000
start commit: cd802e7e5f1e Merge tag 'for-linus' of git://git.kernel.org..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=11cf6cd4580000
console output: https://syzkaller.appspot.com/x/log.txt?x=16cf6cd4580000
kernel config: https://syzkaller.appspot.com/x/.config?x=91c351a0f6229e67
dashboard link: https://syzkaller.appspot.com/bug?extid=99d6c66dbbc484f50e1c
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=143a7768580000
Reported-by: syzbot+99d6c66dbbc484f50e1c@syzkaller.appspotmail.com
Fixes: a368ecde8a50 ("USB: core: Fix duplicate endpoint bug by clearing reserved bits in the descriptor")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2025-05-13 15:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-30 17:36 [syzbot] KASAN: use-after-free Read in em28xx_init_extension (2) syzbot
2022-03-30 18:46 ` Pavel Skripkin
2025-05-13 15:02 ` syzbot [this message]
2025-05-13 15:11 ` [syzbot] [usb?] [media?] " Alan Stern
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=68235ee9.050a0220.f2294.09fc.GAE@google.com \
--to=syzbot+99d6c66dbbc484f50e1c@syzkaller.appspotmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=hdanton@sina.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=paskripkin@gmail.com \
--cc=stern@rowland.harvard.edu \
--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