==================================================================
BUG: KASAN: slab-out-of-bounds in soft_cursor+0x96b/0xa30 drivers/video/fbdev/core/softcursor.c:61
Read of size 1 at addr ffff888098aec6f0 by task kworker/1:2/9075

CPU: 1 PID: 9075 Comm: kworker/1:2 Not tainted 4.19.184-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Workqueue: events_power_efficient fb_flashcursor
Call Trace:
 __dump_stack lib/dump_stack.c:77 [inline]
 dump_stack+0x1fc/0x2ef lib/dump_stack.c:118
 print_address_description.cold+0x54/0x219 mm/kasan/report.c:256
 kasan_report_error.cold+0x8a/0x1b9 mm/kasan/report.c:354
 kasan_report mm/kasan/report.c:412 [inline]
 __asan_report_load1_noabort+0x88/0x90 mm/kasan/report.c:430
 soft_cursor+0x96b/0xa30 drivers/video/fbdev/core/softcursor.c:61
 bit_cursor+0x1126/0x1740 drivers/video/fbdev/core/bitblit.c:377
 fb_flashcursor+0x38c/0x430 drivers/video/fbdev/core/fbcon.c:379
 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

Allocated by task 14416:
 __do_kmalloc mm/slab.c:3727 [inline]
 __kmalloc+0x15a/0x3c0 mm/slab.c:3736
 kmalloc include/linux/slab.h:520 [inline]
 fbcon_set_font+0x34f/0x8a0 drivers/video/fbdev/core/fbcon.c:2479
 con_font_set drivers/tty/vt/vt.c:4537 [inline]
 con_font_op+0x94b/0xf20 drivers/tty/vt/vt.c:4581
 vt_ioctl+0x116b/0x2380 drivers/tty/vt/vt_ioctl.c:938
 tty_ioctl+0x5b0/0x15c0 drivers/tty/tty_io.c:2669
 vfs_ioctl fs/ioctl.c:46 [inline]
 file_ioctl fs/ioctl.c:501 [inline]
 do_vfs_ioctl+0xcdb/0x12e0 fs/ioctl.c:688
 ksys_ioctl+0x9b/0xc0 fs/ioctl.c:705
 __do_sys_ioctl fs/ioctl.c:712 [inline]
 __se_sys_ioctl fs/ioctl.c:710 [inline]
 __x64_sys_ioctl+0x6f/0xb0 fs/ioctl.c:710
 do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293
 entry_SYSCALL_64_after_hwframe+0x49/0xbe

Freed by task 4700:
 __cache_free mm/slab.c:3503 [inline]
 kfree+0xcc/0x210 mm/slab.c:3822
 kernfs_fop_release+0x120/0x190 fs/kernfs/file.c:783
 __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

The buggy address belongs to the object at ffff888098aec5c0
 which belongs to the cache kmalloc-512 of size 512
The buggy address is located 304 bytes inside of
 512-byte region [ffff888098aec5c0, ffff888098aec7c0)
The buggy address belongs to the page:
page:ffffea000262bb00 count:1 mapcount:0 mapping:ffff88813bff0940 index:0xffff888098aec0c0
flags: 0xfff00000000100(slab)
raw: 00fff00000000100 ffffea00025ae448 ffffea000263c408 ffff88813bff0940
raw: ffff888098aec0c0 ffff888098aec0c0 0000000100000002 0000000000000000
page dumped because: kasan: bad access detected

Memory state around the buggy address:
 ffff888098aec580: fc fc fc fc fc fc fc fc 00 00 00 00 00 00 00 00
 ffff888098aec600: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>ffff888098aec680: 00 00 00 00 00 00 00 00 00 00 fc fc fc fc fc fc
                                                             ^
 ffff888098aec700: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc
 ffff888098aec780: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc
==================================================================