kernel BUG at mm/vmalloc.c:LINE!

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: d7e78d08 Linux 4.14.195
git tree: linux-4.14.y
console output: https://syzkaller.appspot.com/x/log.txt?x=10149b05900000
kernel config: https://syzkaller.appspot.com/x/.config?x=6608b656f49b4e8c
dashboard link: https://syzkaller.appspot.com/bug?extid=af8b33d63d587841c0b9
compiler: gcc (GCC) 10.1.0-syz 20200507

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

------------[ cut here ]------------
kernel BUG at mm/vmalloc.c:1544!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
Modules linked in:
CPU: 1 PID: 15484 Comm: syz-executor.0 Not tainted 4.14.195-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
task: ffff888051c0c640 task.stack: ffff888085238000
RIP: 0010:__vunmap+0x1e2/0x300 mm/vmalloc.c:1544
RSP: 0018:ffff88808523fc78 EFLAGS: 00010297
RAX: ffff888051c0c640 RBX: 0000000000000063 RCX: 0000000000000000
RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000286
RBP: ffff8880964f5300 R08: ffffed100a3dec00 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000000 R12: dffffc0000000000
R13: ffffed1012c9ea64 R14: ffffed1012c9ea65 R15: 0000000000000000
FS: 0000000003052940(0000) GS:ffff8880aeb00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00000000004fe930 CR3: 0000000056e62000 CR4: 00000000001406e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
vfree+0x4b/0xd0 mm/vmalloc.c:1612
kcov_put kernel/kcov.c:104 [inline]
kcov_put kernel/kcov.c:101 [inline]
kcov_close+0x1b/0x30 kernel/kcov.c:188
__fput+0x25f/0x7a0 fs/file_table.c:210
task_work_run+0x11f/0x190 kernel/task_work.c:113
exit_task_work include/linux/task_work.h:22 [inline]
do_exit+0xa08/0x27f0 kernel/exit.c:865
do_group_exit+0x100/0x2e0 kernel/exit.c:962
SYSC_exit_group kernel/exit.c:973 [inline]
SyS_exit_group+0x19/0x20 kernel/exit.c:971
do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x46/0xbb
RIP: 0033:0x45d5b9
RSP: 002b:00007fffb14fa858 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 000000000045d5b9
RDX: 0000000000416e20 RSI: 000000000000000c RDI: 0000000000000000
RBP: 00000000000000f8 R08: 000000000000001a R09: 00000000b14faae8
R10: 0000000003052940 R11: 0000000000000246 R12: 0000000000418e70
R13: 00007fffb14faae8 R14: 0000000000000000 R15: 0000000000000000
Code: 00 48 8b 55 20 48 63 c3 4c 8d 3c c2 4c 89 fa 48 c1 ea 03 42 80 3c 22 00 0f 85 97 00 00 00 4d 8b 3f 4d 85 ff 75 a4 e8 8e 36 dc ff <0f> 0b e8 87 36 dc ff 48 8b 54 24 08 48 b8 00 00 00 00 00 fc ff
RIP: __vunmap+0x1e2/0x300 mm/vmalloc.c:1544 RSP: ffff88808523fc78
---[ end trace a12d0d433fc8c642 ]---


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