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

Status: upstream: reported on 2026/08/07 05:50
Reported-by: syzbot+5de3002e518884f6bfb9@syzkaller.appspotmail.com
First crash: 4d22h, last: 8h15m
▶ ▼ Similar bugs (10)
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 1750d 2043d 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 7363 1h25m 282d 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 3d19h 5d15h 0/3 upstream: reported on 2026/08/06 13:30
upstream KASAN: vmalloc-out-of-bounds Write in imageblit (5) fbdev 21 syz, C 1075 286d 337d 29/29 fixed on 2025/10/29 21:02
upstream KASAN: vmalloc-out-of-bounds Write in imageblit (4) fbdev 21 syz, C 3869 341d 720d 29/29 fixed on 2025/09/04 16:57
upstream KASAN: vmalloc-out-of-bounds Write in imageblit (3) fbdev 21 2 1113d 1109d 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 1439d 1726d 22/29 fixed on 2023/02/24 13:50
linux-6.6 KASAN: vmalloc-out-of-bounds Write in imageblit 21 7 48m 6d14h 0/2 upstream: reported on 2026/08/05 13:55
upstream KASAN: vmalloc-out-of-bounds Write in sys_imageblit fbdev 21 syz, C 91 2069d 2436d 0/29 auto-obsoleted due to no activity on 2022/12/09 01:09
upstream BUG: unable to handle kernel paging request in sys_imageblit fbdev 8 syz 16 2066d 2436d 0/29 auto-obsoleted due to no activity on 2022/08/31 01:46

Sample crash report:
==================================================================
BUG: KASAN: vmalloc-out-of-bounds in fast_imageblit drivers/video/fbdev/core/sysimgblt.c:257 [inline]
BUG: KASAN: vmalloc-out-of-bounds in sys_imageblit+0x1ba8/0x25d0 drivers/video/fbdev/core/sysimgblt.c:323
Write of size 4 at addr ffffc90004a59000 by task syz.7.1653/12706

CPU: 0 PID: 12706 Comm: syz.7.1653 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/24/2026
Call Trace:
 <TASK>
 dump_stack_lvl+0x188/0x24e lib/dump_stack.c:106
 print_address_description mm/kasan/report.c:316 [inline]
 print_report+0xa8/0x210 mm/kasan/report.c:420
 kasan_report+0x10b/0x140 mm/kasan/report.c:524
 fast_imageblit drivers/video/fbdev/core/sysimgblt.c:257 [inline]
 sys_imageblit+0x1ba8/0x25d0 drivers/video/fbdev/core/sysimgblt.c:323
 drm_fb_helper_sys_imageblit+0x2e/0x510 drivers/gpu/drm/drm_fb_helper.c:864
 soft_cursor+0x9fd/0xc30 drivers/video/fbdev/core/softcursor.c:74
 bit_cursor+0x1699/0x1f00 drivers/video/fbdev/core/bitblit.c:404
 hide_cursor+0x7f/0x320 drivers/tty/vt/vt.c:907
 do_con_write+0x1dd/0x6c40 drivers/tty/vt/vt.c:2927
 con_write+0x1f/0x40 drivers/tty/vt/vt.c:3295
 do_output_char+0x58a/0x960 drivers/tty/n_tty.c:440
 __process_echoes+0x2a2/0x8f0 drivers/tty/n_tty.c:727
 flush_echoes drivers/tty/n_tty.c:817 [inline]
 __receive_buf drivers/tty/n_tty.c:1625 [inline]
 n_tty_receive_buf_common+0xda0/0x1470 drivers/tty/n_tty.c:1721
 paste_selection+0x321/0x4c0 drivers/tty/vt/selection.c:409
 vt_ioctl+0x449/0x1cc0 drivers/tty/vt/vt_ioctl.c:762
 tty_ioctl+0x7e6/0xba0 drivers/tty/tty_io.c:2776
 vfs_ioctl fs/ioctl.c:51 [inline]
 __do_sys_ioctl fs/ioctl.c:870 [inline]
 __se_sys_ioctl+0xfa/0x170 fs/ioctl.c:856
 do_syscall_x64 arch/x86/entry/common.c:46 [inline]
 do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:76
 entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7fe74579e0d9
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:00007fe7466c6028 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007fe745a25fa0 RCX: 00007fe74579e0d9
RDX: 0000200000000000 RSI: 000000000000541c RDI: 0000000000000003
RBP: 00007fe745835024 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fe745a26038 R14: 00007fe745a25fa0 R15: 00007ffdd360c6e8
 </TASK>

The buggy address belongs to a 0-page vmalloc region starting at 0xffffc90004759000 allocated at drm_gem_shmem_vmap_locked drivers/gpu/drm/drm_gem_shmem_helper.c:320 [inline]
The buggy address belongs to a 0-page vmalloc region starting at 0xffffc90004759000 allocated at drm_gem_shmem_vmap+0x347/0x4d0 drivers/gpu/drm/drm_gem_shmem_helper.c:367
Memory state around the buggy address:
 ffffc90004a58f00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
 ffffc90004a58f80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>ffffc90004a59000: f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8
                   ^
 ffffc90004a59080: f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8
 ffffc90004a59100: f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8
==================================================================

Crashes (12):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2026/08/11 07:18 linux-6.1.y e4f7d8be268e 508909ea .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan KASAN: vmalloc-out-of-bounds Write in imageblit
2026/08/10 22:46 linux-6.1.y e4f7d8be268e 508909ea .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan KASAN: vmalloc-out-of-bounds Write in imageblit
2026/08/10 22:45 linux-6.1.y e4f7d8be268e 508909ea .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan KASAN: vmalloc-out-of-bounds Write in imageblit
2026/08/07 05:49 linux-6.1.y 03f3a99e8e93 c38879ea .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan KASAN: vmalloc-out-of-bounds Write in imageblit
2026/08/11 02:49 linux-6.1.y e4f7d8be268e 508909ea .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 KASAN: vmalloc-out-of-bounds Write in imageblit
2026/08/11 02:47 linux-6.1.y e4f7d8be268e 508909ea .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 KASAN: vmalloc-out-of-bounds Write in imageblit
2026/08/11 02:47 linux-6.1.y e4f7d8be268e 508909ea .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 KASAN: vmalloc-out-of-bounds Write in imageblit
2026/08/11 02:47 linux-6.1.y e4f7d8be268e 508909ea .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 KASAN: vmalloc-out-of-bounds Write in imageblit
2026/08/08 19:56 linux-6.1.y e4f7d8be268e 5d63f80b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 KASAN: vmalloc-out-of-bounds Write in imageblit
2026/08/11 20:15 linux-6.1.y e4f7d8be268e 71790083 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 BUG: unable to handle kernel paging request in imageblit
2026/08/10 16:03 linux-6.1.y e4f7d8be268e 5d63f80b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 BUG: unable to handle kernel paging request in imageblit
2026/08/10 12:25 linux-6.1.y e4f7d8be268e 5d63f80b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 BUG: unable to handle kernel paging request in imageblit
* Struck through repros no longer work on HEAD.