From: syzbot <syzbot+lista86ace36a0e89d7697c1@syzkaller.appspotmail.com>
To: krzk@kernel.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly nfc report (Sep 2026)
Date: Sat, 26 Sep 2026 05:33:24 -0700 [thread overview]
Message-ID: <6ab7bb94.dc2998a4.2261f5.0056.GAE@google.com> (raw)
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, 2 new issues were detected and 2 were fixed.
In total, 10 issues are still open and 34 have already been fixed.
There is also 1 low-priority issue.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 325 Yes WARNING in port100_send_cmd_async/usb_submit_urb (3)
https://syzkaller.appspot.com/bug?extid=89f5f8143d8e62af2b61
<2> 4 Yes INFO: task hung in pn533_usb_probe
https://syzkaller.appspot.com/bug?extid=8996fbe184c5b84f89d4
<3> 4 Yes general protection fault in nfcmrvl_bulk_complete
https://syzkaller.appspot.com/bug?extid=59d5e6a8ed04e6a000c8
<4> 1 No WARNING in nci_unregister_device (2)
https://syzkaller.appspot.com/bug?extid=c2d417f06523d8133c6a
---
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-09-26 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=6ab7bb94.dc2998a4.2261f5.0056.GAE@google.com \
--to=syzbot+lista86ace36a0e89d7697c1@syzkaller.appspotmail.com \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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®