==================================================================
BUG: KASAN: global-out-of-bounds in memcpy syzkaller/managers/linux-4-14/kernel/./include/linux/string.h:372 [inline]
BUG: KASAN: global-out-of-bounds in soft_cursor+0x442/0xa50 syzkaller/managers/linux-4-14/kernel/drivers/video/fbdev/core/softcursor.c:70
Read of size 31 at addr ffffffff87cf5552 by task syz-executor.0/15111

CPU: 0 PID: 15111 Comm: syz-executor.0 Not tainted 4.14.218-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
 __dump_stack syzkaller/managers/linux-4-14/kernel/lib/dump_stack.c:17 [inline]
 dump_stack+0x1b2/0x281 syzkaller/managers/linux-4-14/kernel/lib/dump_stack.c:58
 print_address_description.cold+0x5/0x1d3 syzkaller/managers/linux-4-14/kernel/mm/kasan/report.c:252
 kasan_report_error.cold+0x8a/0x191 syzkaller/managers/linux-4-14/kernel/mm/kasan/report.c:351
 kasan_report+0x6f/0x80 syzkaller/managers/linux-4-14/kernel/mm/kasan/report.c:409
 memcpy+0x20/0x50 syzkaller/managers/linux-4-14/kernel/mm/kasan/kasan.c:302
 memcpy syzkaller/managers/linux-4-14/kernel/./include/linux/string.h:372 [inline]
 soft_cursor+0x442/0xa50 syzkaller/managers/linux-4-14/kernel/drivers/video/fbdev/core/softcursor.c:70
 bit_cursor+0xf7a/0x1580 syzkaller/managers/linux-4-14/kernel/drivers/video/fbdev/core/bitblit.c:377
 fbcon_cursor+0x480/0x640 syzkaller/managers/linux-4-14/kernel/drivers/video/fbdev/core/fbcon.c:1287
 hide_cursor+0x7a/0x2a0 syzkaller/managers/linux-4-14/kernel/drivers/tty/vt/vt.c:590
 redraw_screen+0x29d/0x790 syzkaller/managers/linux-4-14/kernel/drivers/tty/vt/vt.c:680
 vc_do_resize+0xc08/0xe00 syzkaller/managers/linux-4-14/kernel/drivers/tty/vt/vt.c:974
 vt_ioctl+0x1884/0x1d50 syzkaller/managers/linux-4-14/kernel/drivers/tty/vt/vt_ioctl.c:905
 tty_ioctl+0x50f/0x13c0 syzkaller/managers/linux-4-14/kernel/drivers/tty/tty_io.c:2661
 vfs_ioctl syzkaller/managers/linux-4-14/kernel/fs/ioctl.c:46 [inline]
 file_ioctl syzkaller/managers/linux-4-14/kernel/fs/ioctl.c:500 [inline]
 do_vfs_ioctl+0x75a/0xff0 syzkaller/managers/linux-4-14/kernel/fs/ioctl.c:684
 SYSC_ioctl syzkaller/managers/linux-4-14/kernel/fs/ioctl.c:701 [inline]
 SyS_ioctl+0x7f/0xb0 syzkaller/managers/linux-4-14/kernel/fs/ioctl.c:692
 do_syscall_64+0x1d5/0x640 syzkaller/managers/linux-4-14/kernel/arch/x86/entry/common.c:292
 entry_SYSCALL_64_after_hwframe+0x46/0xbb
RIP: 0033:0x465b09
RSP: 002b:00007f4257e62188 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 000000000056bf60 RCX: 0000000000465b09
RDX: 0000000020000000 RSI: 000000000000560a RDI: 0000000000000003
RBP: 00000000004b069f R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 000000000056bf60
R13: 00007fff85f6030f R14: 00007f4257e62300 R15: 0000000000022000

The buggy address belongs to the variable:
 str__msr__trace_system_name+0xf2/0xb00

Memory state around the buggy address:
 ffffffff87cf5400: fa fa fa fa 00 03 fa fa fa fa fa fa 04 fa fa fa
 ffffffff87cf5480: fa fa fa fa 00 03 fa fa fa fa fa fa 05 fa fa fa
>ffffffff87cf5500: fa fa fa fa 00 06 fa fa fa fa fa fa 00 00 00 03
                                                 ^
 ffffffff87cf5580: fa fa fa fa 00 02 fa fa fa fa fa fa 00 00 07 fa
 ffffffff87cf5600: fa fa fa fa 00 00 07 fa fa fa fa fa 00 00 01 fa
==================================================================