==================================================================
BUG: KASAN: use-after-free in __fb_pad_aligned_buffer include/linux/fb.h:654 [inline]
BUG: KASAN: use-after-free in bit_putcs_aligned drivers/video/fbdev/core/bitblit.c:96 [inline]
BUG: KASAN: use-after-free in bit_putcs+0x103a/0x1bf0 drivers/video/fbdev/core/bitblit.c:185
Read of size 1 at addr ffff8880965c6c08 by task syz-executor.3/4153

CPU: 1 PID: 4153 Comm: syz-executor.3 Not tainted 5.9.0-rc2-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+0x1f0/0x31e lib/dump_stack.c:118
 print_address_description+0x66/0x620 mm/kasan/report.c:383
 __kasan_report mm/kasan/report.c:513 [inline]
 kasan_report+0x132/0x1d0 mm/kasan/report.c:530
 __fb_pad_aligned_buffer include/linux/fb.h:654 [inline]
 bit_putcs_aligned drivers/video/fbdev/core/bitblit.c:96 [inline]
 bit_putcs+0x103a/0x1bf0 drivers/video/fbdev/core/bitblit.c:185
 fbcon_putcs+0x790/0xaf0 drivers/video/fbdev/core/fbcon.c:1362
 con_flush drivers/tty/vt/vt.c:2574 [inline]
 do_con_write+0x2853/0xd580 drivers/tty/vt/vt.c:2904
 con_write+0x20/0x40 drivers/tty/vt/vt.c:3249
 process_output_block drivers/tty/n_tty.c:595 [inline]
 n_tty_write+0xcbf/0x1170 drivers/tty/n_tty.c:2333
 do_tty_write drivers/tty/tty_io.c:962 [inline]
 tty_write+0x593/0x940 drivers/tty/tty_io.c:1046
 vfs_write+0x2d3/0xd10 fs/read_write.c:576
 ksys_write+0x11b/0x220 fs/read_write.c:631
 do_syscall_64+0x31/0x70 arch/x86/entry/common.c:46
 entry_SYSCALL_64_after_hwframe+0x44/0xa9
RIP: 0033:0x45d579
Code: 5d 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 2b b4 fb ff c3 66 2e 0f 1f 84 00 00 00 00
RSP: 002b:00007f05bffc7c78 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 00000000000387c0 RCX: 000000000045d579
RDX: 0000000000001006 RSI: 0000000020001440 RDI: 0000000000000004
RBP: 000000000118cf80 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 000000000118cf4c
R13: 00007ffef1123e7f R14: 00007f05bffc89c0 R15: 000000000118cf4c

Allocated by task 3676:
 kasan_save_stack mm/kasan/common.c:48 [inline]
 kasan_set_track mm/kasan/common.c:56 [inline]
 __kasan_kmalloc+0x100/0x130 mm/kasan/common.c:461
 kmem_cache_alloc_trace+0x1f6/0x2f0 mm/slab.c:3550
 kmalloc include/linux/slab.h:554 [inline]
 kzalloc include/linux/slab.h:666 [inline]
 alloc_bprm+0x57/0x6a0 fs/exec.c:1602
 kernel_execve+0x49/0x970 fs/exec.c:2047
 call_usermodehelper_exec_async+0x204/0x330 kernel/umh.c:101
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:294

The buggy address belongs to the object at ffff8880965c6c00
 which belongs to the cache kmalloc-512 of size 512
The buggy address is located 8 bytes inside of
 512-byte region [ffff8880965c6c00, ffff8880965c6e00)
The buggy address belongs to the page:
page:00000000001c1744 refcount:1 mapcount:0 mapping:0000000000000000 index:0xffff8880965c6000 pfn:0x965c6
flags: 0xfffe0000000200(slab)
raw: 00fffe0000000200 ffffea00028bcd08 ffffea00029cf248 ffff8880aa440600
raw: ffff8880965c6000 ffff8880965c6000 0000000100000001 0000000000000000
page dumped because: kasan: bad access detected

Memory state around the buggy address:
 ffff8880965c6b00: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc
 ffff8880965c6b80: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc
>ffff8880965c6c00: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
                      ^
 ffff8880965c6c80: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
 ffff8880965c6d00: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
==================================================================