WARNING in packet_sock_destruct

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 2cae3e25 Linux 4.19.179
git tree: linux-4.19.y
console output: https://syzkaller.appspot.com/x/log.txt?x=149737dad00000
kernel config: https://syzkaller.appspot.com/x/.config?x=6362bb600ad8bf7
dashboard link: https://syzkaller.appspot.com/bug?extid=ec4f274c5996bfc4a4ae

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+ec4f27...@syzkaller.appspotmail.com

netlink: 8 bytes leftover after parsing attributes in process `syz-executor.1'.
EXT4-fs (loop4): mounted filesystem without journal. Opts: ,errors=continue
------------[ cut here ]------------
WARNING: CPU: 0 PID: 9897 at net/packet/af_packet.c:1289 packet_sock_destruct.cold+0x29/0x49 net/packet/af_packet.c:1289
Kernel panic - not syncing: panic_on_warn set ...

CPU: 0 PID: 9897 Comm: syz-executor.5 Not tainted 4.19.179-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0x1fc/0x2ef lib/dump_stack.c:118
panic+0x26a/0x50e kernel/panic.c:186
__warn.cold+0x20/0x5a kernel/panic.c:541
report_bug+0x262/0x2b0 lib/bug.c:186
fixup_bug arch/x86/kernel/traps.c:178 [inline]
fixup_bug arch/x86/kernel/traps.c:173 [inline]
do_error_trap+0x1d7/0x310 arch/x86/kernel/traps.c:296
netlink: 44 bytes leftover after parsing attributes in process `syz-executor.1'.
netlink: 8 bytes leftover after parsing attributes in process `syz-executor.1'.
invalid_op+0x14/0x20 arch/x86/entry/entry_64.S:1038
RIP: 0010:packet_sock_destruct.cold+0x29/0x49 net/packet/af_packet.c:1289
Code: ea e8 09 bb 51 f9 48 c7 c7 80 ed 5a 89 e8 b7 60 e0 ff 0f 0b e9 19 cf 0d ff e8 f1 ba 51 f9 48 c7 c7 80 ed 5a 89 e8 9f 60 e0 ff <0f> 0b e9 ab ce 0d ff e8 d9 ba 51 f9 48 89 ee 48 c7 c7 e0 ed 5a 89
RSP: 0018:ffff888046847c80 EFLAGS: 00010286
RAX: 0000000000000024 RBX: 0000000000000300 RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffffffff814de3d1 RDI: ffffed1008d08f82
RBP: ffff888054188dc0 R08: 0000000000000024 R09: 0000000000000000
R10: 0000000000000005 R11: 0000000000000000 R12: ffff888054188f98
R13: ffff888054188dc0 R14: ffff88804a233b00 R15: ffff888054188e40
__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
sock_put include/net/sock.h:1711 [inline]
packet_release+0x890/0xb70 net/packet/af_packet.c:3088
__sock_release+0xcd/0x2a0 net/socket.c:579
sock_close+0x15/0x20 net/socket.c:1140
__fput+0x2ce/0x890 fs/file_table.c:278
task_work_run+0x148/0x1c0 kernel/task_work.c:113
tracehook_notify_resume include/linux/tracehook.h:193 [inline]
exit_to_usermode_loop+0x251/0x2a0 arch/x86/entry/common.c:167
prepare_exit_to_usermode arch/x86/entry/common.c:198 [inline]
syscall_return_slowpath arch/x86/entry/common.c:271 [inline]
do_syscall_64+0x538/0x620 arch/x86/entry/common.c:296
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x41927b
Code: 0f 05 48 3d 00 f0 ff ff 77 45 c3 0f 1f 40 00 48 83 ec 18 89 7c 24 0c e8 63 fc ff ff 8b 7c 24 0c 41 89 c0 b8 03 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 35 44 89 c7 89 44 24 0c e8 a1 fc ff ff 8b 44
RSP: 002b:00007ffcc6504d10 EFLAGS: 00000293 ORIG_RAX: 0000000000000003
RAX: 0000000000000000 RBX: 0000000000000006 RCX: 000000000041927b
RDX: 0000000000000000 RSI: 0000000008c9f5bb RDI: 0000000000000005
RBP: 0000000000000001 R08: 0000000000000000 R09: 0000001b2f822c64
R10: 0000000000000000 R11: 0000000000000293 R12: 000000000056c9e0
R13: 000000000056c9e0 R14: 000000000056bf60 R15: 00000000000210a6
Kernel Offset: disabled
Rebooting in 86400 seconds..


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

Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.