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

0 views
Skip to first unread message

syzbot

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

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

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

Some of the still happening issues:

Ref Crashes Repro Title
<1> 1387 Yes INFO: task hung in nfc_rfkill_set_block
https://syzkaller.appspot.com/bug?extid=3e3c2f8ca188e30b1427
<2> 622 Yes INFO: task hung in rfkill_unregister (3)
https://syzkaller.appspot.com/bug?extid=bb540a4bbfb4ae3b425d
<3> 184 Yes KMSAN: uninit-value in nci_ntf_packet (3)
https://syzkaller.appspot.com/bug?extid=3f8fa0edaa75710cd66e
<4> 110 Yes INFO: task hung in rfkill_sync_work
https://syzkaller.appspot.com/bug?extid=9ef743bba3a17c756174
<5> 31 Yes WARNING in nfc_rfkill_set_block
https://syzkaller.appspot.com/bug?extid=535bbe83dfc3ae8d4be3
<6> 1 No WARNING: locking bug in nci_close_device (3)
https://syzkaller.appspot.com/bug?extid=f9c5fd1a0874f9069dce

The report will be sent to: [net...@vger.kernel.org kr...@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