From: syzbot <syzbot+list9ab3a27a20db62b86eb3@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, linux-nfc@lists.01.org,
netdev@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly nfc report (Jul 2023)
Date: Wed, 05 Jul 2023 06:10:52 -0700 [thread overview]
Message-ID: <00000000000015d25a05ffbd21d5@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, 1 new issues were detected and 0 were fixed.
In total, 9 issues are still open and 17 have been fixed so far.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 109 Yes BUG: corrupted list in nfc_llcp_unregister_device
https://syzkaller.appspot.com/bug?extid=81232c4a81a886e2b580
<2> 80 Yes BUG: corrupted list in nfc_llcp_register_device
https://syzkaller.appspot.com/bug?extid=c1d0a03d305972dbbe14
<3> 69 Yes INFO: task hung in nfc_rfkill_set_block
https://syzkaller.appspot.com/bug?extid=3e3c2f8ca188e30b1427
<4> 61 Yes KASAN: use-after-free Read in nfc_llcp_find_local
https://syzkaller.appspot.com/bug?extid=e7ac69e6a5d806180b40
<5> 19 Yes BUG: corrupted list in nfc_llcp_local_put
https://syzkaller.appspot.com/bug?extid=ecb2ae7b1add2a4120de
---
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:[~2023-07-05 13:10 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=00000000000015d25a05ffbd21d5@google.com \
--to=syzbot+list9ab3a27a20db62b86eb3@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfc@lists.01.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.