From: syzbot <syzbot+0a031a76585d1c7e737d@syzkaller.appspotmail.com>
To: bentiss@kernel.org, ccc194101@163.com, chenchangcheng@kylinos.cn,
jeffinphilip14@gmail.com, jikos@kernel.org, jkosina@suse.com,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-usb@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [input?] [usb?] WARNING: ODEBUG bug in corsair_remove
Date: Fri, 28 Aug 2026 06:26:02 -0700 [thread overview]
Message-ID: <6a918c6a.27659fcc.2ceef7.001a.GAE@google.com> (raw)
In-Reply-To: <6a802643.9ebadd4d.20b15e.000a.GAE@google.com>
syzbot has bisected this issue to:
commit eb51c9f8cb4f064981d9c6cae13de8eda280785d
Author: Chen Changcheng <chenchangcheng@kylinos.cn>
Date: Mon Jul 27 01:35:00 2026 +0000
HID: corsair: cancel worker before unregistering LED to fix use-after-free
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=12580379580000
start commit: 73e3f0710014 Merge tag 'nfs-for-7.3-1' of git://git.linux-..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=11580379580000
console output: https://syzkaller.appspot.com/x/log.txt?x=16580379580000
kernel config: https://syzkaller.appspot.com/x/.config?x=9efed59cf70d6280
dashboard link: https://syzkaller.appspot.com/bug?extid=0a031a76585d1c7e737d
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11e6e579580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=13e4ed49580000
Reported-by: syzbot+0a031a76585d1c7e737d@syzkaller.appspotmail.com
Fixes: eb51c9f8cb4f ("HID: corsair: cancel worker before unregistering LED to fix use-after-free")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2026-08-28 13:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-15 8:41 [syzbot] [input?] [usb?] WARNING: ODEBUG bug in corsair_remove syzbot
2026-08-26 22:22 ` syzbot
2026-08-28 13:26 ` syzbot [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=6a918c6a.27659fcc.2ceef7.001a.GAE@google.com \
--to=syzbot+0a031a76585d1c7e737d@syzkaller.appspotmail.com \
--cc=bentiss@kernel.org \
--cc=ccc194101@163.com \
--cc=chenchangcheng@kylinos.cn \
--cc=jeffinphilip14@gmail.com \
--cc=jikos@kernel.org \
--cc=jkosina@suse.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--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.