==================================================================
BUG: KASAN: global-out-of-bounds in memcpy include/linux/string.h:373 [inline]
BUG: KASAN: global-out-of-bounds in soft_cursor+0x44b/0xa30 drivers/video/fbdev/core/softcursor.c:70
Read of size 32 at addr ffffffff88b65e70 by task syz-executor.0/22188

CPU: 1 PID: 22188 Comm: syz-executor.0 Not tainted 4.19.161-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/0x2fe lib/dump_stack.c:118
 print_address_description.cold+0x5/0x219 mm/kasan/report.c:256
 kasan_report_error.cold+0x8a/0x1c7 mm/kasan/report.c:354
 kasan_report+0x8f/0x96 mm/kasan/report.c:412
 memcpy+0x20/0x50 mm/kasan/kasan.c:302
 memcpy include/linux/string.h:373 [inline]
 soft_cursor+0x44b/0xa30 drivers/video/fbdev/core/softcursor.c:70
 bit_cursor+0x1126/0x1740 drivers/video/fbdev/core/bitblit.c:377
 fbcon_cursor+0x523/0x700 drivers/video/fbdev/core/fbcon.c:1309
 hide_cursor+0x85/0x2c0 drivers/tty/vt/vt.c:902
 update_region+0x136/0x190 drivers/tty/vt/vt.c:700
 vcs_write+0x403/0xc30 drivers/tty/vt/vc_screen.c:604
 __vfs_write+0xf7/0x770 fs/read_write.c:485
 vfs_write+0x1f3/0x540 fs/read_write.c:549
 ksys_write+0x12b/0x2a0 fs/read_write.c:599
 do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293
 entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x45de79
Code: 0d b4 fb ff c3 66 2e 0f 1f 84 00 00 00 00 00 66 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 0f 83 db b3 fb ff c3 66 2e 0f 1f 84 00 00 00 00
RSP: 002b:00007fdc876cdc68 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 0000000000000003 RCX: 000000000045de79
RDX: 0000000000000121 RSI: 00000000200000c0 RDI: 0000000000000003
RBP: 000000000118bf60 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 000000000118bf2c
R13: 00007ffc773939df R14: 00007fdc876ce9c0 R15: 000000000118bf2c

The buggy address belongs to the variable:
 str__msr__trace_system_name+0x10/0xbc0

Memory state around the buggy address:
 ffffffff88b65d00: 00 01 fa fa fa fa fa fa 00 00 00 00 01 fa fa fa
 ffffffff88b65d80: fa fa fa fa 00 00 00 05 fa fa fa fa 00 00 00 00
>ffffffff88b65e00: fa fa fa fa 00 03 fa fa fa fa fa fa 04 fa fa fa
                                                             ^
 ffffffff88b65e80: fa fa fa fa 00 03 fa fa fa fa fa fa 05 fa fa fa
 ffffffff88b65f00: fa fa fa fa 00 06 fa fa fa fa fa fa 00 00 00 03
==================================================================