general protection fault in klist_iter_exit

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 830a059c Linux 4.19.186
git tree: linux-4.19.y
console output: https://syzkaller.appspot.com/x/log.txt?x=13e48441d00000
kernel config: https://syzkaller.appspot.com/x/.config?x=7415cc95f9edb7b9
dashboard link: https://syzkaller.appspot.com/bug?extid=984f0e794042ceadb043

Unfortunately, I don't have any reproducer for this issue yet.

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+984f0e...@syzkaller.appspotmail.com

R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000001
R13: 00007ffd57e6bfdf R14: 00007faa6aaba300 R15: 0000000000022000
kasan: CONFIG_KASAN_INLINE enabled
kasan: GPF could be caused by NULL-ptr deref or user memory access
general protection fault: 0000 [#1] PREEMPT SMP KASAN
CPU: 1 PID: 17429 Comm: kworker/1:4 Not tainted 4.19.186-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:314
Code: 66 0f 1f 84 00 00 00 00 00 41 54 55 53 48 89 fb e8 74 b0 75 f9 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 4b b0 75 f9 31 f6
RSP: 0018:ffff88809d65fc48 EFLAGS: 00010202
RAX: dffffc0000000000 RBX: 0000000000000000 RCX: 0000000000000000
RDX: 0000000000000001 RSI: ffffffff87ecad4c RDI: 0000000000000000
RBP: 0000000000000008 R08: 0000000000000000 R09: fffffbfff15cfae8
R10: ffffffff8ae7d747 R11: 0000000000000000 R12: 0000000000000000
R13: ffffffff896eb200 R14: ffff8880ba12a840 R15: ffff8880ba12f000
FS: 0000000000000000(0000) GS:ffff8880ba100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f36c00400f8 CR3: 00000000b4775000 CR4: 00000000001426e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
nfc_device_iter_exit net/nfc/nfc.h:133 [inline]
nfc_genl_dump_devices_done+0x31/0x50 net/nfc/netlink.c:658
genl_lock_done+0x82/0xc0 net/netlink/genetlink.c:495
netlink_sock_destruct+0x96/0x280 net/netlink/af_netlink.c:398
__sk_destruct+0x4b/0x8a0 net/core/sock.c:1559
sk_destruct net/core/sock.c:1599 [inline]
__sk_free+0x165/0x3b0 net/core/sock.c:1610
sk_free+0x3b/0x50 net/core/sock.c:1621
process_one_work+0x864/0x1570 kernel/workqueue.c:2152
worker_thread+0x64c/0x1130 kernel/workqueue.c:2295
kthread+0x33f/0x460 kernel/kthread.c:259
ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:415
Modules linked in:
---[ end trace ad3c95f996038baa ]---
RIP: 0010:klist_iter_exit+0x21/0x80 lib/klist.c:314
Code: 66 0f 1f 84 00 00 00 00 00 41 54 55 53 48 89 fb e8 74 b0 75 f9 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 4b b0 75 f9 31 f6
RSP: 0018:ffff88809d65fc48 EFLAGS: 00010202
RAX: dffffc0000000000 RBX: 0000000000000000 RCX: 0000000000000000
RDX: 0000000000000001 RSI: ffffffff87ecad4c RDI: 0000000000000000
RBP: 0000000000000008 R08: 0000000000000000 R09: fffffbfff15cfae8
R10: ffffffff8ae7d747 R11: 0000000000000000 R12: 0000000000000000
R13: ffffffff896eb200 R14: ffff8880ba12a840 R15: ffff8880ba12f000
FS: 0000000000000000(0000) GS:ffff8880ba100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f36c00400f8 CR3: 00000000aa58b000 CR4: 00000000001426e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400


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

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

[syzbot]

syzbot has found a reproducer for the following issue on:

HEAD commit: 830a059c Linux 4.19.186
git tree: linux-4.19.y

console output: https://syzkaller.appspot.com/x/log.txt?x=1470177ed00000

kernel config: https://syzkaller.appspot.com/x/.config?x=7415cc95f9edb7b9
dashboard link: https://syzkaller.appspot.com/bug?extid=984f0e794042ceadb043

syz repro: https://syzkaller.appspot.com/x/repro.syz?x=17677996d00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1202fd16d00000

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+984f0e...@syzkaller.appspotmail.com

RBP: 0000000000000004 R08: 0000000000000001 R09: 00007ffcca5b66b0
R10: 0000000000000000 R11: 0000000000000246 R12: 00000000021fc2b8
R13: 0000000000000000 R14: 00007ffcca5b6660 R15: 00007ffcca5b6668

kasan: CONFIG_KASAN_INLINE enabled
kasan: GPF could be caused by NULL-ptr deref or user memory access
general protection fault: 0000 [#1] PREEMPT SMP KASAN

CPU: 0 PID: 5 Comm: kworker/0:0 Not tainted 4.19.186-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:314
Code: 66 0f 1f 84 00 00 00 00 00 41 54 55 53 48 89 fb e8 74 b0 75 f9 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 4b b0 75 f9 31 f6

RSP: 0018:ffff8880b5a37c48 EFLAGS: 00010202

RAX: dffffc0000000000 RBX: 0000000000000000 RCX: 0000000000000000
RDX: 0000000000000001 RSI: ffffffff87ecad4c RDI: 0000000000000000
RBP: 0000000000000008 R08: 0000000000000000 R09: fffffbfff15cfae8

R10: ffffffff8ae7d747 R11: 0000000000074071 R12: 0000000000000000
R13: ffffffff896eb200 R14: ffff8880ba02a840 R15: ffff8880ba02f000
FS: 0000000000000000(0000) GS:ffff8880ba000000(0000) knlGS:0000000000000000

CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033

CR2: 00005611cd37a268 CR3: 0000000009e6d000 CR4: 00000000001406f0