From: syzbot <syzbot+list3acbd9912bd634558b43@syzkaller.appspotmail.com>
To: dakr@kernel.org, driver-core@lists.linux.dev,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly driver-core report (Oct 2026)
Date: Mon, 26 Oct 2026 13:33:43 -0700 [thread overview]
Message-ID: <6adfb927.3a3d6196.2ecadf.001f.GAE@google.com> (raw)
Hello driver-core maintainers/developers,
This is a 31-day syzbot report for the driver-core subsystem.
All related reports/information can be found at:
https://syzkaller.appspot.com/upstream/s/driver-core
During the period, 1 new issues were detected and 1 were fixed.
In total, 26 issues are still open and 4 have already been fixed.
There are also 14 low-priority issues.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 137 Yes KASAN: slab-use-after-free Read in disable_device
https://syzkaller.appspot.com/bug?extid=4393dfdddf166f2de2b0
<2> 91 No INFO: task hung in usb_disable_device (2)
https://syzkaller.appspot.com/bug?extid=5cf28d3643d94bfb0821
<3> 35 Yes KASAN: slab-use-after-free Read in lockref_get (2)
https://syzkaller.appspot.com/bug?extid=227dbc9afd022922d624
<4> 22 Yes KASAN: global-out-of-bounds Read in uevent_store
https://syzkaller.appspot.com/bug?extid=d164947c037324221043
<5> 18 Yes general protection fault in bus_remove_device
https://syzkaller.appspot.com/bug?extid=87188222c77c0dbbdb4d
<6> 11 Yes INFO: task hung in unbind_store
https://syzkaller.appspot.com/bug?extid=fd7be5ad9795b7f29df3
<7> 4 Yes BUG: unable to handle kernel paging request in usb_driver_release_interface
https://syzkaller.appspot.com/bug?extid=863936f50214e843ae0c
<8> 14 Yes KASAN: global-out-of-bounds Read in bus_uevent_store
https://syzkaller.appspot.com/bug?extid=9a321aea9d851b299486
<9> 8 Yes KASAN: slab-use-after-free Write in do_bad_area
https://syzkaller.appspot.com/bug?extid=7bf725ed337e37307001
<10> 7 No KASAN: slab-use-after-free Read in remove_one_compat_dev
https://syzkaller.appspot.com/bug?extid=7db35adbc02c5b86d4e0
---
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-26 20: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=6adfb927.3a3d6196.2ecadf.001f.GAE@google.com \
--to=syzbot+list3acbd9912bd634558b43@syzkaller.appspotmail.com \
--cc=dakr@kernel.org \
--cc=driver-core@lists.linux.dev \
--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®