[syzbot-moderation] Monthly kvm report (Jan 2026)

0 views
Skip to first unread message

syzbot

unread,
Jan 11, 2026, 7:32:27 AM (20 hours ago) Jan 11
to syzkaller-upst...@googlegroups.com
Hello kvm maintainers/developers,

This is a 31-day syzbot report for the kvm subsystem.
All related reports/information can be found at:
https://syzkaller.appspot.com/upstream/s/kvm

During the period, 1 new issues were detected and 0 were fixed.
In total, 7 issues are still open and 65 have already been fixed.

Some of the still happening issues:

Ref Crashes Repro Title
<1> 660 Yes WARNING: locking bug in kvm_xen_set_evtchn_fast
https://syzkaller.appspot.com/bug?extid=919877893c9d28162dc2
<2> 49 Yes WARNING in __kvm_gpc_refresh (3)
https://syzkaller.appspot.com/bug?extid=cde12433b6c56f55d9ed
<3> 12 No INFO: task hung in kvm_swap_active_memslots (2)
https://syzkaller.appspot.com/bug?extid=5c566b850d6ab6f0427a
<4> 4 Yes WARNING in kvm_read_guest_offset_cached
https://syzkaller.appspot.com/bug?extid=bc0e18379a290e5edfe4

The report will be sent to: [k...@vger.kernel.org linux-...@vger.kernel.org].

---
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 syzk...@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

If the report looks fine to you, reply with:
#syz upstream

To regenerate the report, reply with:
#syz regenerate

You may send multiple commands in a single email message.
Reply all
Reply to author
Forward
0 new messages