From: syzbot <syzbot+e690c969b19e84332c36@syzkaller.appspotmail.com>
To: bodefang@126.com, davem@davemloft.net, geliangtang@gmail.com,
kuba@kernel.org, laniel_francis@privacyrequired.com,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] general protection fault in klist_iter_exit
Date: Sat, 06 Mar 2021 18:19:17 -0800 [thread overview]
Message-ID: <000000000000bc002505bce8f18b@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: d310ec03 Merge tag 'perf-core-2021-02-17' of git://git.ker..
git tree: net-next
console output: https://syzkaller.appspot.com/x/log.txt?x=1350c796d00000
kernel config: https://syzkaller.appspot.com/x/.config?x=2b8307379601586a
dashboard link: https://syzkaller.appspot.com/bug?extid=e690c969b19e84332c36
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1480f5b6d00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=13e826dad00000
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+e690c969b19e84332c36@syzkaller.appspotmail.com
general protection fault, probably for non-canonical address 0xdffffc0000000001: 0000 [#1] PREEMPT SMP KASAN
KASAN: null-ptr-deref in range [0x0000000000000008-0x000000000000000f]
CPU: 0 PID: 3882 Comm: kworker/0:3 Not tainted 5.11.0-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Workqueue: events netlink_sock_destruct_work
RIP: 0010:klist_iter_exit+0x21/0x80 lib/klist.c:313
Code: 66 0f 1f 84 00 00 00 00 00 41 54 55 53 48 89 fb e8 24 30 98 fd 48 8d 6b 08 48 b8 00 00 00 00 00 fc ff df 48 89 ea 48 c1 ea 03 <80> 3c 02 00 75 40 4c 8b 63 08 4d 85 e4 74 2e e8 fb 2f 98 fd 31 f6
RSP: 0018:ffffc9000312fbf8 EFLAGS: 00010202
RAX: dffffc0000000000 RBX: 0000000000000000 RCX: 0000000000000000
RDX: 0000000000000001 RSI: ffffffff83daa98c RDI: 0000000000000000
RBP: 0000000000000008 R08: 0000000000000000 R09: ffffffff8d6fc867
R10: fffffbfff1adf90c R11: 1ffffffff1ede8aa R12: ffff888143cb7540
R13: 0000000000000000 R14: ffff88801bce1520 R15: ffff8880b9c34980
FS: 0000000000000000(0000) GS:ffff8880b9c00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f2a3562f1f0 CR3: 0000000017103000 CR4: 00000000001506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
nfc_device_iter_exit net/nfc/nfc.h:121 [inline]
nfc_genl_dump_devices_done+0x31/0x50 net/nfc/netlink.c:639
genl_lock_done+0x8d/0x100 net/netlink/genetlink.c:636
netlink_sock_destruct+0x96/0x2b0 net/netlink/af_netlink.c:398
__sk_destruct+0x4b/0x900 net/core/sock.c:1795
sk_destruct+0xbd/0xe0 net/core/sock.c:1839
__sk_free+0xef/0x3d0 net/core/sock.c:1850
sk_free+0x78/0xa0 net/core/sock.c:1861
process_one_work+0x98d/0x1600 kernel/workqueue.c:2275
worker_thread+0x64c/0x1120 kernel/workqueue.c:2421
kthread+0x3b1/0x4a0 kernel/kthread.c:292
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:294
---
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.
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
syzbot can test patches for this issue, for details see:
https://goo.gl/tpsmEJ#testing-patches
reply other threads:[~2021-03-07 2:21 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=000000000000bc002505bce8f18b@google.com \
--to=syzbot+e690c969b19e84332c36@syzkaller.appspotmail.com \
--cc=bodefang@126.com \
--cc=davem@davemloft.net \
--cc=geliangtang@gmail.com \
--cc=kuba@kernel.org \
--cc=laniel_francis@privacyrequired.com \
--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 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.