KASAN: vmalloc-out-of-bounds Write in imageblit

Status: upstream: reported on 2026/08/05 13:55
Reported-by: syzbot+802bf88adfebfa7c354f@syzkaller.appspotmail.com
First crash: 3d09h, last: 1d01h
▶ ▼ Similar bugs (9)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream KASAN: vmalloc-out-of-bounds Write in imageblit fbdev 21 syz, C 104 1747d 2040d 20/29 fixed on 2021/11/10 00:50
upstream KASAN: vmalloc-out-of-bounds Write in imageblit (6) prio:high fbdev 21 syz, C 7215 2h31m 279d 0/29 upstream: reported C repro on 2025/11/02 21:10
linux-5.15 KASAN: vmalloc-out-of-bounds Write in imageblit 21 4 14h49m 2d09h 0/3 upstream: reported on 2026/08/06 13:30
linux-6.1 KASAN: vmalloc-out-of-bounds Write in imageblit 21 2 3h27m 1d17h 0/3 upstream: reported on 2026/08/07 05:50
upstream KASAN: vmalloc-out-of-bounds Write in imageblit (5) fbdev 21 syz, C 1075 283d 334d 29/29 fixed on 2025/10/29 21:02
upstream KASAN: vmalloc-out-of-bounds Write in imageblit (4) fbdev 21 syz, C 3869 338d 717d 29/29 fixed on 2025/09/04 16:57
upstream KASAN: vmalloc-out-of-bounds Write in imageblit (3) fbdev 21 2 1110d 1106d 0/29 auto-obsoleted due to no activity on 2023/10/23 10:50
upstream KASAN: vmalloc-out-of-bounds Write in imageblit (2) fbdev 21 syz, C done 701 1435d 1723d 22/29 fixed on 2023/02/24 13:50
upstream KASAN: vmalloc-out-of-bounds Write in sys_imageblit fbdev 21 syz, C 91 2066d 2433d 0/29 auto-obsoleted due to no activity on 2022/12/09 01:09

Sample crash report:
==================================================================
BUG: KASAN: vmalloc-out-of-bounds in fast_imageblit drivers/video/fbdev/core/sysimgblt.c:276 [inline]
BUG: KASAN: vmalloc-out-of-bounds in sys_imageblit+0x2114/0x25d0 drivers/video/fbdev/core/sysimgblt.c:323
Write of size 4 at addr ffffc90003cd9ff8 by task syz.9.2347/14211

CPU: 0 PID: 14211 Comm: syz.9.2347 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/24/2026
Call Trace:
 <TASK>
 dump_stack_lvl+0x18c/0x250 lib/dump_stack.c:106
 print_address_description mm/kasan/report.c:364 [inline]
 print_report+0xa8/0x210 mm/kasan/report.c:468
 kasan_report+0x117/0x150 mm/kasan/report.c:581
 fast_imageblit drivers/video/fbdev/core/sysimgblt.c:276 [inline]
 sys_imageblit+0x2114/0x25d0 drivers/video/fbdev/core/sysimgblt.c:323
 drm_fbdev_generic_defio_imageblit+0x2c/0x110 drivers/gpu/drm/drm_fbdev_generic.c:37
 cw_putcs_aligned drivers/video/fbdev/core/fbcon_cw.c:110 [inline]
 cw_putcs+0x15f3/0x18a0 drivers/video/fbdev/core/fbcon_cw.c:158
 fbcon_putcs+0x35c/0x520 drivers/video/fbdev/core/fbcon.c:1301
 do_update_region+0x4e9/0x640 drivers/tty/vt/vt.c:623
 redraw_screen+0xa30/0x1000 drivers/tty/vt/vt.c:983
 vc_do_resize+0x1256/0x17f0 drivers/tty/vt/vt.c:1291
 fbcon_do_set_font+0xb5c/0x1ae0 drivers/video/fbdev/core/fbcon.c:2440
 con_font_set drivers/tty/vt/vt.c:4629 [inline]
 con_font_op+0xc3c/0xf60 drivers/tty/vt/vt.c:4676
 vt_k_ioctl drivers/tty/vt/vt_ioctl.c:474 [inline]
 vt_ioctl+0x1a07/0x1f00 drivers/tty/vt/vt_ioctl.c:752
 tty_ioctl+0x91e/0xdc0 drivers/tty/tty_io.c:2779
 vfs_ioctl fs/ioctl.c:51 [inline]
 __do_sys_ioctl fs/ioctl.c:871 [inline]
 __se_sys_ioctl+0xfd/0x170 fs/ioctl.c:857
 do_syscall_x64 arch/x86/entry/common.c:46 [inline]
 do_syscall_64+0x55/0xb0 arch/x86/entry/common.c:76
 entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7fcd8f19e0d9
Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 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 73 01 c3 48 c7 c1 e8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fcd90050028 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007fcd8f426180 RCX: 00007fcd8f19e0d9
RDX: 00002000000001c0 RSI: 0000000000004b72 RDI: 0000000000000006
RBP: 00007fcd8f235024 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fcd8f426218 R14: 00007fcd8f426180 R15: 00007ffdf8c56148
 </TASK>

The buggy address belongs to a 0-page vmalloc region starting at 0xffffc90003cda000 allocated at drm_gem_shmem_vmap+0x3c4/0x650 drivers/gpu/drm/drm_gem_shmem_helper.c:340
Memory state around the buggy address:
 ffffc90003cd9e80: f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8
 ffffc90003cd9f00: f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8
>ffffc90003cd9f80: f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8
                                                                ^
 ffffc90003cda000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
 ffffc90003cda080: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
==================================================================

Crashes (3):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2026/08/07 22:13 linux-6.6.y 6436c12a2ced e4ef95d6 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan KASAN: vmalloc-out-of-bounds Write in imageblit
2026/08/07 05:33 linux-6.6.y 80dfb0405055 c38879ea .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan KASAN: vmalloc-out-of-bounds Write in imageblit
2026/08/05 13:55 linux-6.6.y aa0e49877a2e 52aa2820 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan KASAN: vmalloc-out-of-bounds Write in imageblit
* Struck through repros no longer work on HEAD.