From: syzbot <syzbot+list4c580c10329f11ac634c@syzkaller.appspotmail.com>
To: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly input report (Oct 2026)
Date: Sun, 25 Oct 2026 05:33:25 -0700 [thread overview]
Message-ID: <6addf715.67317f00.38c4bc.0080.GAE@google.com> (raw)
Hello input maintainers/developers,
This is a 31-day syzbot report for the input subsystem.
All related reports/information can be found at:
https://syzkaller.appspot.com/upstream/s/input
During the period, 3 new issues were detected and 3 were fixed.
In total, 32 issues are still open and 70 have already been fixed.
There are also 3 low-priority issues.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 1516 Yes KASAN: slab-out-of-bounds Read in mcp2221_raw_event (2)
https://syzkaller.appspot.com/bug?extid=1018672fe70298606e5f
<2> 873 Yes WARNING: ODEBUG bug in corsair_remove
https://syzkaller.appspot.com/bug?extid=0a031a76585d1c7e737d
<3> 368 Yes possible deadlock in __kernfs_remove (3)
https://syzkaller.appspot.com/bug?extid=1075f6dc93f398c1857e
<4> 42 Yes INFO: task hung in devres_release_group (2)
https://syzkaller.appspot.com/bug?extid=d789904ff97c2f3dac88
<5> 28 Yes INFO: task hung in __input_unregister_device (5)
https://syzkaller.appspot.com/bug?extid=78e2288f58b881ed3c45
<6> 12 No KASAN: slab-use-after-free Read in k90_backlight_work
https://syzkaller.appspot.com/bug?extid=abcedffc9201f2bb66c2
<7> 2 Yes memory leak in __usbhid_submit_report (2)
https://syzkaller.appspot.com/bug?extid=e2c057ea576d2644e2be
---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzkaller@googlegroups.com.
To disable reminders for individual bugs, reply with the following command:
#syz set <Ref> no-reminders
To change bug's subsystems, reply with:
#syz set <Ref> subsystems: new-subsystem
You may send multiple commands in a single email message.
reply other threads:[~2026-10-25 12:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=6addf715.67317f00.38c4bc.0080.GAE@google.com \
--to=syzbot+list4c580c10329f11ac634c@syzkaller.appspotmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®