* KASAN: global-out-of-bounds Read in bit_putcs
@ 2019-12-05 16:46 ` syzbot
0 siblings, 0 replies; 15+ messages in thread
From: syzbot @ 2019-12-05 16:46 UTC (permalink / raw)
To: b.zolnierkie, dri-devel, linux-fbdev, linux-kernel, syzkaller-bugs
Hello,
syzbot found the following crash on:
HEAD commit: 2f13437b Merge tag 'trace-v5.5-2' of git://git.kernel.org/..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=104fcc2ae00000
kernel config: https://syzkaller.appspot.com/x/.config?x=608557e57ce07817
dashboard link: https://syzkaller.appspot.com/bug?extid=38a3699c7eaf165b97a6
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
Unfortunately, I don't have any reproducer for this crash yet.
IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+38a3699c7eaf165b97a6@syzkaller.appspotmail.com
==================================================================
BUG: KASAN: global-out-of-bounds in __fb_pad_aligned_buffer
include/linux/fb.h:655 [inline]
BUG: KASAN: global-out-of-bounds in bit_putcs_aligned
drivers/video/fbdev/core/bitblit.c:96 [inline]
BUG: KASAN: global-out-of-bounds in bit_putcs+0xd5d/0xf10
drivers/video/fbdev/core/bitblit.c:185
Read of size 1 at addr ffffffff88725b0f by task syz-executor.3/14961
CPU: 0 PID: 14961 Comm: syz-executor.3 Not tainted 5.4.0-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+0x197/0x210 lib/dump_stack.c:118
print_address_description.constprop.0.cold+0x5/0x30b mm/kasan/report.c:374
__kasan_report.cold+0x1b/0x41 mm/kasan/report.c:506
kasan_report+0x12/0x20 mm/kasan/common.c:638
__asan_report_load1_noabort+0x14/0x20 mm/kasan/generic_report.c:132
__fb_pad_aligned_buffer include/linux/fb.h:655 [inline]
bit_putcs_aligned drivers/video/fbdev/core/bitblit.c:96 [inline]
bit_putcs+0xd5d/0xf10 drivers/video/fbdev/core/bitblit.c:185
fbcon_putcs+0x33c/0x3e0 drivers/video/fbdev/core/fbcon.c:1353
do_update_region+0x328/0x6f0 drivers/tty/vt/vt.c:667
redraw_screen+0x676/0x7d0 drivers/tty/vt/vt.c:1011
fbcon_do_set_font+0x829/0x960 drivers/video/fbdev/core/fbcon.c:2605
fbcon_copy_font+0x12c/0x190 drivers/video/fbdev/core/fbcon.c:2620
con_font_copy drivers/tty/vt/vt.c:4594 [inline]
con_font_op+0x69a/0x1250 drivers/tty/vt/vt.c:4609
vt_ioctl+0x181a/0x26d0 drivers/tty/vt/vt_ioctl.c:965
tty_ioctl+0xa37/0x14f0 drivers/tty/tty_io.c:2660
vfs_ioctl fs/ioctl.c:47 [inline]
file_ioctl fs/ioctl.c:545 [inline]
do_vfs_ioctl+0x977/0x14e0 fs/ioctl.c:732
ksys_ioctl+0xab/0xd0 fs/ioctl.c:749
__do_sys_ioctl fs/ioctl.c:756 [inline]
__se_sys_ioctl fs/ioctl.c:754 [inline]
__x64_sys_ioctl+0x73/0xb0 fs/ioctl.c:754
do_syscall_64+0xfa/0x790 arch/x86/entry/common.c:294
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x45a679
Code: ad b6 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 7b b6 fb ff c3 66 2e 0f 1f 84 00 00 00 00
RSP: 002b:00007f8bdf6cfc78 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 0000000000000003 RCX: 000000000045a679
RDX: 0000000020000400 RSI: 0000000000004b72 RDI: 0000000000000003
RBP: 000000000075bf20 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007f8bdf6d06d4
R13: 00000000004c37ab R14: 00000000004d8c38 R15: 00000000ffffffff
The buggy address belongs to the variable:
oid_index+0x3cf/0xb80
Memory state around the buggy address:
ffffffff88725a00: 03 fa fa fa fa fa fa fa 03 fa fa fa fa fa fa fa
ffffffff88725a80: 03 fa fa fa fa fa fa fa 00 07 fa fa fa fa fa fa
> ffffffff88725b00: 00 07 fa fa fa fa fa fa 00 06 fa fa fa fa fa fa
^
ffffffff88725b80: 06 fa fa fa fa fa fa fa 00 00 00 04 fa fa fa fa
ffffffff88725c00: 00 00 fa fa fa fa fa fa 00 00 06 fa fa fa fa fa
==================================================================
---
This bug is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzkaller@googlegroups.com.
syzbot will keep track of this bug report. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
^ permalink raw reply [flat|nested] 15+ messages in thread
* KASAN: global-out-of-bounds Read in bit_putcs
@ 2019-12-05 16:46 ` syzbot
0 siblings, 0 replies; 15+ messages in thread
From: syzbot @ 2019-12-05 16:46 UTC (permalink / raw)
To: b.zolnierkie, dri-devel, linux-fbdev, linux-kernel, syzkaller-bugs
Hello,
syzbot found the following crash on:
HEAD commit: 2f13437b Merge tag 'trace-v5.5-2' of git://git.kernel.org/..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x\x104fcc2ae00000
kernel config: https://syzkaller.appspot.com/x/.config?x`8557e57ce07817
dashboard link: https://syzkaller.appspot.com/bug?extid8a3699c7eaf165b97a6
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
Unfortunately, I don't have any reproducer for this crash yet.
IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+38a3699c7eaf165b97a6@syzkaller.appspotmail.com
=================================
BUG: KASAN: global-out-of-bounds in __fb_pad_aligned_buffer
include/linux/fb.h:655 [inline]
BUG: KASAN: global-out-of-bounds in bit_putcs_aligned
drivers/video/fbdev/core/bitblit.c:96 [inline]
BUG: KASAN: global-out-of-bounds in bit_putcs+0xd5d/0xf10
drivers/video/fbdev/core/bitblit.c:185
Read of size 1 at addr ffffffff88725b0f by task syz-executor.3/14961
CPU: 0 PID: 14961 Comm: syz-executor.3 Not tainted 5.4.0-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+0x197/0x210 lib/dump_stack.c:118
print_address_description.constprop.0.cold+0x5/0x30b mm/kasan/report.c:374
__kasan_report.cold+0x1b/0x41 mm/kasan/report.c:506
kasan_report+0x12/0x20 mm/kasan/common.c:638
__asan_report_load1_noabort+0x14/0x20 mm/kasan/generic_report.c:132
__fb_pad_aligned_buffer include/linux/fb.h:655 [inline]
bit_putcs_aligned drivers/video/fbdev/core/bitblit.c:96 [inline]
bit_putcs+0xd5d/0xf10 drivers/video/fbdev/core/bitblit.c:185
fbcon_putcs+0x33c/0x3e0 drivers/video/fbdev/core/fbcon.c:1353
do_update_region+0x328/0x6f0 drivers/tty/vt/vt.c:667
redraw_screen+0x676/0x7d0 drivers/tty/vt/vt.c:1011
fbcon_do_set_font+0x829/0x960 drivers/video/fbdev/core/fbcon.c:2605
fbcon_copy_font+0x12c/0x190 drivers/video/fbdev/core/fbcon.c:2620
con_font_copy drivers/tty/vt/vt.c:4594 [inline]
con_font_op+0x69a/0x1250 drivers/tty/vt/vt.c:4609
vt_ioctl+0x181a/0x26d0 drivers/tty/vt/vt_ioctl.c:965
tty_ioctl+0xa37/0x14f0 drivers/tty/tty_io.c:2660
vfs_ioctl fs/ioctl.c:47 [inline]
file_ioctl fs/ioctl.c:545 [inline]
do_vfs_ioctl+0x977/0x14e0 fs/ioctl.c:732
ksys_ioctl+0xab/0xd0 fs/ioctl.c:749
__do_sys_ioctl fs/ioctl.c:756 [inline]
__se_sys_ioctl fs/ioctl.c:754 [inline]
__x64_sys_ioctl+0x73/0xb0 fs/ioctl.c:754
do_syscall_64+0xfa/0x790 arch/x86/entry/common.c:294
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x45a679
Code: ad b6 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 7b b6 fb ff c3 66 2e 0f 1f 84 00 00 00 00
RSP: 002b:00007f8bdf6cfc78 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 0000000000000003 RCX: 000000000045a679
RDX: 0000000020000400 RSI: 0000000000004b72 RDI: 0000000000000003
RBP: 000000000075bf20 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007f8bdf6d06d4
R13: 00000000004c37ab R14: 00000000004d8c38 R15: 00000000ffffffff
The buggy address belongs to the variable:
oid_index+0x3cf/0xb80
Memory state around the buggy address:
ffffffff88725a00: 03 fa fa fa fa fa fa fa 03 fa fa fa fa fa fa fa
ffffffff88725a80: 03 fa fa fa fa fa fa fa 00 07 fa fa fa fa fa fa
> ffffffff88725b00: 00 07 fa fa fa fa fa fa 00 06 fa fa fa fa fa fa
^
ffffffff88725b80: 06 fa fa fa fa fa fa fa 00 00 00 04 fa fa fa fa
ffffffff88725c00: 00 00 fa fa fa fa fa fa 00 00 06 fa fa fa fa fa
=================================
---
This bug is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzkaller@googlegroups.com.
syzbot will keep track of this bug report. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
^ permalink raw reply [flat|nested] 15+ messages in thread
* KASAN: global-out-of-bounds Read in bit_putcs
@ 2019-12-05 16:46 ` syzbot
0 siblings, 0 replies; 15+ messages in thread
From: syzbot @ 2019-12-05 16:46 UTC (permalink / raw)
To: b.zolnierkie, dri-devel, linux-fbdev, linux-kernel, syzkaller-bugs
Hello,
syzbot found the following crash on:
HEAD commit: 2f13437b Merge tag 'trace-v5.5-2' of git://git.kernel.org/..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=104fcc2ae00000
kernel config: https://syzkaller.appspot.com/x/.config?x=608557e57ce07817
dashboard link: https://syzkaller.appspot.com/bug?extid=38a3699c7eaf165b97a6
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
Unfortunately, I don't have any reproducer for this crash yet.
IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+38a3699c7eaf165b97a6@syzkaller.appspotmail.com
==================================================================
BUG: KASAN: global-out-of-bounds in __fb_pad_aligned_buffer
include/linux/fb.h:655 [inline]
BUG: KASAN: global-out-of-bounds in bit_putcs_aligned
drivers/video/fbdev/core/bitblit.c:96 [inline]
BUG: KASAN: global-out-of-bounds in bit_putcs+0xd5d/0xf10
drivers/video/fbdev/core/bitblit.c:185
Read of size 1 at addr ffffffff88725b0f by task syz-executor.3/14961
CPU: 0 PID: 14961 Comm: syz-executor.3 Not tainted 5.4.0-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+0x197/0x210 lib/dump_stack.c:118
print_address_description.constprop.0.cold+0x5/0x30b mm/kasan/report.c:374
__kasan_report.cold+0x1b/0x41 mm/kasan/report.c:506
kasan_report+0x12/0x20 mm/kasan/common.c:638
__asan_report_load1_noabort+0x14/0x20 mm/kasan/generic_report.c:132
__fb_pad_aligned_buffer include/linux/fb.h:655 [inline]
bit_putcs_aligned drivers/video/fbdev/core/bitblit.c:96 [inline]
bit_putcs+0xd5d/0xf10 drivers/video/fbdev/core/bitblit.c:185
fbcon_putcs+0x33c/0x3e0 drivers/video/fbdev/core/fbcon.c:1353
do_update_region+0x328/0x6f0 drivers/tty/vt/vt.c:667
redraw_screen+0x676/0x7d0 drivers/tty/vt/vt.c:1011
fbcon_do_set_font+0x829/0x960 drivers/video/fbdev/core/fbcon.c:2605
fbcon_copy_font+0x12c/0x190 drivers/video/fbdev/core/fbcon.c:2620
con_font_copy drivers/tty/vt/vt.c:4594 [inline]
con_font_op+0x69a/0x1250 drivers/tty/vt/vt.c:4609
vt_ioctl+0x181a/0x26d0 drivers/tty/vt/vt_ioctl.c:965
tty_ioctl+0xa37/0x14f0 drivers/tty/tty_io.c:2660
vfs_ioctl fs/ioctl.c:47 [inline]
file_ioctl fs/ioctl.c:545 [inline]
do_vfs_ioctl+0x977/0x14e0 fs/ioctl.c:732
ksys_ioctl+0xab/0xd0 fs/ioctl.c:749
__do_sys_ioctl fs/ioctl.c:756 [inline]
__se_sys_ioctl fs/ioctl.c:754 [inline]
__x64_sys_ioctl+0x73/0xb0 fs/ioctl.c:754
do_syscall_64+0xfa/0x790 arch/x86/entry/common.c:294
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x45a679
Code: ad b6 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 7b b6 fb ff c3 66 2e 0f 1f 84 00 00 00 00
RSP: 002b:00007f8bdf6cfc78 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 0000000000000003 RCX: 000000000045a679
RDX: 0000000020000400 RSI: 0000000000004b72 RDI: 0000000000000003
RBP: 000000000075bf20 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007f8bdf6d06d4
R13: 00000000004c37ab R14: 00000000004d8c38 R15: 00000000ffffffff
The buggy address belongs to the variable:
oid_index+0x3cf/0xb80
Memory state around the buggy address:
ffffffff88725a00: 03 fa fa fa fa fa fa fa 03 fa fa fa fa fa fa fa
ffffffff88725a80: 03 fa fa fa fa fa fa fa 00 07 fa fa fa fa fa fa
> ffffffff88725b00: 00 07 fa fa fa fa fa fa 00 06 fa fa fa fa fa fa
^
ffffffff88725b80: 06 fa fa fa fa fa fa fa 00 00 00 04 fa fa fa fa
ffffffff88725c00: 00 00 fa fa fa fa fa fa 00 00 06 fa fa fa fa fa
==================================================================
---
This bug is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzkaller@googlegroups.com.
syzbot will keep track of this bug report. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: KASAN: global-out-of-bounds Read in bit_putcs
2019-12-05 16:46 ` syzbot
(?)
@ 2019-12-06 16:34 ` syzbot
-1 siblings, 0 replies; 15+ messages in thread
From: syzbot @ 2019-12-06 16:34 UTC (permalink / raw)
To: b.zolnierkie, dri-devel, linux-fbdev, linux-kernel, syzkaller-bugs
syzbot has found a reproducer for the following crash on:
HEAD commit: b0d4beaa Merge branch 'next.autofs' of git://git.kernel.or..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1015a90ee00000
kernel config: https://syzkaller.appspot.com/x/.config?x=f07a23020fd7d21a
dashboard link: https://syzkaller.appspot.com/bug?extid=38a3699c7eaf165b97a6
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1795d941e00000
IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+38a3699c7eaf165b97a6@syzkaller.appspotmail.com
==================================================================
BUG: KASAN: global-out-of-bounds in __fb_pad_aligned_buffer
include/linux/fb.h:655 [inline]
BUG: KASAN: global-out-of-bounds in bit_putcs_aligned
drivers/video/fbdev/core/bitblit.c:96 [inline]
BUG: KASAN: global-out-of-bounds in bit_putcs+0xd5d/0xf10
drivers/video/fbdev/core/bitblit.c:185
Read of size 1 at addr ffffffff88726a41 by task syz-executor.5/9415
CPU: 1 PID: 9415 Comm: syz-executor.5 Not tainted 5.4.0-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+0x197/0x210 lib/dump_stack.c:118
print_address_description.constprop.0.cold+0x5/0x30b mm/kasan/report.c:374
__kasan_report.cold+0x1b/0x41 mm/kasan/report.c:506
kasan_report+0x12/0x20 mm/kasan/common.c:639
__asan_report_load1_noabort+0x14/0x20 mm/kasan/generic_report.c:132
__fb_pad_aligned_buffer include/linux/fb.h:655 [inline]
bit_putcs_aligned drivers/video/fbdev/core/bitblit.c:96 [inline]
bit_putcs+0xd5d/0xf10 drivers/video/fbdev/core/bitblit.c:185
fbcon_putcs+0x33c/0x3e0 drivers/video/fbdev/core/fbcon.c:1353
do_update_region+0x42b/0x6f0 drivers/tty/vt/vt.c:677
redraw_screen+0x676/0x7d0 drivers/tty/vt/vt.c:1011
fbcon_do_set_font+0x829/0x960 drivers/video/fbdev/core/fbcon.c:2605
fbcon_copy_font+0x12c/0x190 drivers/video/fbdev/core/fbcon.c:2620
con_font_copy drivers/tty/vt/vt.c:4594 [inline]
con_font_op+0x6b2/0x1270 drivers/tty/vt/vt.c:4609
vt_ioctl+0x181a/0x26d0 drivers/tty/vt/vt_ioctl.c:965
tty_ioctl+0xa37/0x14f0 drivers/tty/tty_io.c:2660
vfs_ioctl fs/ioctl.c:47 [inline]
file_ioctl fs/ioctl.c:545 [inline]
do_vfs_ioctl+0x977/0x14e0 fs/ioctl.c:732
ksys_ioctl+0xab/0xd0 fs/ioctl.c:749
__do_sys_ioctl fs/ioctl.c:756 [inline]
__se_sys_ioctl fs/ioctl.c:754 [inline]
__x64_sys_ioctl+0x73/0xb0 fs/ioctl.c:754
do_syscall_64+0xfa/0x790 arch/x86/entry/common.c:294
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x45a679
Code: ad b6 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 7b b6 fb ff c3 66 2e 0f 1f 84 00 00 00 00
RSP: 002b:00007f5b74dffc78 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 0000000000000003 RCX: 000000000045a679
RDX: 0000000020000000 RSI: 0000000000004b72 RDI: 0000000000000005
RBP: 000000000075bfc8 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007f5b74e006d4
R13: 00000000004c37ab R14: 00000000004d8c38 R15: 00000000ffffffff
The buggy address belongs to the variable:
oid_index+0xb01/0xb80
Memory state around the buggy address:
ffffffff88726900: 00 00 02 fa fa fa fa fa 00 00 00 05 fa fa fa fa
ffffffff88726980: 00 00 00 fa fa fa fa fa 00 00 00 00 00 01 fa fa
> ffffffff88726a00: fa fa fa fa 00 00 00 00 01 fa fa fa fa fa fa fa
^
ffffffff88726a80: 00 00 00 00 fa fa fa fa 00 03 fa fa fa fa fa fa
ffffffff88726b00: 04 fa fa fa fa fa fa fa 00 00 01 fa fa fa fa fa
==================================================================
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: KASAN: global-out-of-bounds Read in bit_putcs
@ 2019-12-06 16:34 ` syzbot
0 siblings, 0 replies; 15+ messages in thread
From: syzbot @ 2019-12-06 16:34 UTC (permalink / raw)
To: b.zolnierkie, dri-devel, linux-fbdev, linux-kernel, syzkaller-bugs
syzbot has found a reproducer for the following crash on:
HEAD commit: b0d4beaa Merge branch 'next.autofs' of git://git.kernel.or..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x\x1015a90ee00000
kernel config: https://syzkaller.appspot.com/x/.config?xð7a23020fd7d21a
dashboard link: https://syzkaller.appspot.com/bug?extid8a3699c7eaf165b97a6
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
syz repro: https://syzkaller.appspot.com/x/repro.syz?x\x1795d941e00000
IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+38a3699c7eaf165b97a6@syzkaller.appspotmail.com
=================================
BUG: KASAN: global-out-of-bounds in __fb_pad_aligned_buffer
include/linux/fb.h:655 [inline]
BUG: KASAN: global-out-of-bounds in bit_putcs_aligned
drivers/video/fbdev/core/bitblit.c:96 [inline]
BUG: KASAN: global-out-of-bounds in bit_putcs+0xd5d/0xf10
drivers/video/fbdev/core/bitblit.c:185
Read of size 1 at addr ffffffff88726a41 by task syz-executor.5/9415
CPU: 1 PID: 9415 Comm: syz-executor.5 Not tainted 5.4.0-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+0x197/0x210 lib/dump_stack.c:118
print_address_description.constprop.0.cold+0x5/0x30b mm/kasan/report.c:374
__kasan_report.cold+0x1b/0x41 mm/kasan/report.c:506
kasan_report+0x12/0x20 mm/kasan/common.c:639
__asan_report_load1_noabort+0x14/0x20 mm/kasan/generic_report.c:132
__fb_pad_aligned_buffer include/linux/fb.h:655 [inline]
bit_putcs_aligned drivers/video/fbdev/core/bitblit.c:96 [inline]
bit_putcs+0xd5d/0xf10 drivers/video/fbdev/core/bitblit.c:185
fbcon_putcs+0x33c/0x3e0 drivers/video/fbdev/core/fbcon.c:1353
do_update_region+0x42b/0x6f0 drivers/tty/vt/vt.c:677
redraw_screen+0x676/0x7d0 drivers/tty/vt/vt.c:1011
fbcon_do_set_font+0x829/0x960 drivers/video/fbdev/core/fbcon.c:2605
fbcon_copy_font+0x12c/0x190 drivers/video/fbdev/core/fbcon.c:2620
con_font_copy drivers/tty/vt/vt.c:4594 [inline]
con_font_op+0x6b2/0x1270 drivers/tty/vt/vt.c:4609
vt_ioctl+0x181a/0x26d0 drivers/tty/vt/vt_ioctl.c:965
tty_ioctl+0xa37/0x14f0 drivers/tty/tty_io.c:2660
vfs_ioctl fs/ioctl.c:47 [inline]
file_ioctl fs/ioctl.c:545 [inline]
do_vfs_ioctl+0x977/0x14e0 fs/ioctl.c:732
ksys_ioctl+0xab/0xd0 fs/ioctl.c:749
__do_sys_ioctl fs/ioctl.c:756 [inline]
__se_sys_ioctl fs/ioctl.c:754 [inline]
__x64_sys_ioctl+0x73/0xb0 fs/ioctl.c:754
do_syscall_64+0xfa/0x790 arch/x86/entry/common.c:294
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x45a679
Code: ad b6 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 7b b6 fb ff c3 66 2e 0f 1f 84 00 00 00 00
RSP: 002b:00007f5b74dffc78 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 0000000000000003 RCX: 000000000045a679
RDX: 0000000020000000 RSI: 0000000000004b72 RDI: 0000000000000005
RBP: 000000000075bfc8 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007f5b74e006d4
R13: 00000000004c37ab R14: 00000000004d8c38 R15: 00000000ffffffff
The buggy address belongs to the variable:
oid_index+0xb01/0xb80
Memory state around the buggy address:
ffffffff88726900: 00 00 02 fa fa fa fa fa 00 00 00 05 fa fa fa fa
ffffffff88726980: 00 00 00 fa fa fa fa fa 00 00 00 00 00 01 fa fa
> ffffffff88726a00: fa fa fa fa 00 00 00 00 01 fa fa fa fa fa fa fa
^
ffffffff88726a80: 00 00 00 00 fa fa fa fa 00 03 fa fa fa fa fa fa
ffffffff88726b00: 04 fa fa fa fa fa fa fa 00 00 01 fa fa fa fa fa
=================================
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: KASAN: global-out-of-bounds Read in bit_putcs
@ 2019-12-06 16:34 ` syzbot
0 siblings, 0 replies; 15+ messages in thread
From: syzbot @ 2019-12-06 16:34 UTC (permalink / raw)
To: b.zolnierkie, dri-devel, linux-fbdev, linux-kernel, syzkaller-bugs
syzbot has found a reproducer for the following crash on:
HEAD commit: b0d4beaa Merge branch 'next.autofs' of git://git.kernel.or..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1015a90ee00000
kernel config: https://syzkaller.appspot.com/x/.config?x=f07a23020fd7d21a
dashboard link: https://syzkaller.appspot.com/bug?extid=38a3699c7eaf165b97a6
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1795d941e00000
IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+38a3699c7eaf165b97a6@syzkaller.appspotmail.com
==================================================================
BUG: KASAN: global-out-of-bounds in __fb_pad_aligned_buffer
include/linux/fb.h:655 [inline]
BUG: KASAN: global-out-of-bounds in bit_putcs_aligned
drivers/video/fbdev/core/bitblit.c:96 [inline]
BUG: KASAN: global-out-of-bounds in bit_putcs+0xd5d/0xf10
drivers/video/fbdev/core/bitblit.c:185
Read of size 1 at addr ffffffff88726a41 by task syz-executor.5/9415
CPU: 1 PID: 9415 Comm: syz-executor.5 Not tainted 5.4.0-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+0x197/0x210 lib/dump_stack.c:118
print_address_description.constprop.0.cold+0x5/0x30b mm/kasan/report.c:374
__kasan_report.cold+0x1b/0x41 mm/kasan/report.c:506
kasan_report+0x12/0x20 mm/kasan/common.c:639
__asan_report_load1_noabort+0x14/0x20 mm/kasan/generic_report.c:132
__fb_pad_aligned_buffer include/linux/fb.h:655 [inline]
bit_putcs_aligned drivers/video/fbdev/core/bitblit.c:96 [inline]
bit_putcs+0xd5d/0xf10 drivers/video/fbdev/core/bitblit.c:185
fbcon_putcs+0x33c/0x3e0 drivers/video/fbdev/core/fbcon.c:1353
do_update_region+0x42b/0x6f0 drivers/tty/vt/vt.c:677
redraw_screen+0x676/0x7d0 drivers/tty/vt/vt.c:1011
fbcon_do_set_font+0x829/0x960 drivers/video/fbdev/core/fbcon.c:2605
fbcon_copy_font+0x12c/0x190 drivers/video/fbdev/core/fbcon.c:2620
con_font_copy drivers/tty/vt/vt.c:4594 [inline]
con_font_op+0x6b2/0x1270 drivers/tty/vt/vt.c:4609
vt_ioctl+0x181a/0x26d0 drivers/tty/vt/vt_ioctl.c:965
tty_ioctl+0xa37/0x14f0 drivers/tty/tty_io.c:2660
vfs_ioctl fs/ioctl.c:47 [inline]
file_ioctl fs/ioctl.c:545 [inline]
do_vfs_ioctl+0x977/0x14e0 fs/ioctl.c:732
ksys_ioctl+0xab/0xd0 fs/ioctl.c:749
__do_sys_ioctl fs/ioctl.c:756 [inline]
__se_sys_ioctl fs/ioctl.c:754 [inline]
__x64_sys_ioctl+0x73/0xb0 fs/ioctl.c:754
do_syscall_64+0xfa/0x790 arch/x86/entry/common.c:294
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x45a679
Code: ad b6 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 7b b6 fb ff c3 66 2e 0f 1f 84 00 00 00 00
RSP: 002b:00007f5b74dffc78 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 0000000000000003 RCX: 000000000045a679
RDX: 0000000020000000 RSI: 0000000000004b72 RDI: 0000000000000005
RBP: 000000000075bfc8 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007f5b74e006d4
R13: 00000000004c37ab R14: 00000000004d8c38 R15: 00000000ffffffff
The buggy address belongs to the variable:
oid_index+0xb01/0xb80
Memory state around the buggy address:
ffffffff88726900: 00 00 02 fa fa fa fa fa 00 00 00 05 fa fa fa fa
ffffffff88726980: 00 00 00 fa fa fa fa fa 00 00 00 00 00 01 fa fa
> ffffffff88726a00: fa fa fa fa 00 00 00 00 01 fa fa fa fa fa fa fa
^
ffffffff88726a80: 00 00 00 00 fa fa fa fa 00 03 fa fa fa fa fa fa
ffffffff88726b00: 04 fa fa fa fa fa fa fa 00 00 01 fa fa fa fa fa
==================================================================
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: KASAN: global-out-of-bounds Read in bit_putcs
2019-12-05 16:46 ` syzbot
(?)
@ 2019-12-18 19:21 ` syzbot
-1 siblings, 0 replies; 15+ messages in thread
From: syzbot @ 2019-12-18 19:21 UTC (permalink / raw)
To: b.zolnierkie, dri-devel, linux-fbdev, linux-kernel, syzkaller-bugs
syzbot has found a reproducer for the following crash on:
HEAD commit: b9c5ef25 Add linux-next specific files for 20191218
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=17d57b46e00000
kernel config: https://syzkaller.appspot.com/x/.config?x=2eb13492323f151f
dashboard link: https://syzkaller.appspot.com/bug?extid=38a3699c7eaf165b97a6
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=13ce1f2ee00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=125727dee00000
Bisection is inconclusive: the bug happens on the oldest tested release.
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=12caa5b6e00000
final crash: https://syzkaller.appspot.com/x/report.txt?x=11caa5b6e00000
console output: https://syzkaller.appspot.com/x/log.txt?x=16caa5b6e00000
IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+38a3699c7eaf165b97a6@syzkaller.appspotmail.com
==================================================================
BUG: KASAN: global-out-of-bounds in __fb_pad_aligned_buffer
include/linux/fb.h:654 [inline]
BUG: KASAN: global-out-of-bounds in bit_putcs_aligned
drivers/video/fbdev/core/bitblit.c:96 [inline]
BUG: KASAN: global-out-of-bounds in bit_putcs+0xd5d/0xf10
drivers/video/fbdev/core/bitblit.c:185
Read of size 1 at addr ffffffff8872bb44 by task syz-executor093/14101
CPU: 1 PID: 14101 Comm: syz-executor093 Not tainted
5.5.0-rc2-next-20191218-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+0x197/0x210 lib/dump_stack.c:118
print_address_description.constprop.0.cold+0x5/0x30b mm/kasan/report.c:374
__kasan_report.cold+0x1b/0x41 mm/kasan/report.c:506
kasan_report+0x12/0x20 mm/kasan/common.c:639
__asan_report_load1_noabort+0x14/0x20 mm/kasan/generic_report.c:132
__fb_pad_aligned_buffer include/linux/fb.h:654 [inline]
bit_putcs_aligned drivers/video/fbdev/core/bitblit.c:96 [inline]
bit_putcs+0xd5d/0xf10 drivers/video/fbdev/core/bitblit.c:185
fbcon_putcs+0x33c/0x3e0 drivers/video/fbdev/core/fbcon.c:1353
do_update_region+0x42b/0x6f0 drivers/tty/vt/vt.c:677
redraw_screen+0x676/0x7d0 drivers/tty/vt/vt.c:1011
fbcon_do_set_font+0x829/0x960 drivers/video/fbdev/core/fbcon.c:2605
fbcon_copy_font+0x12c/0x190 drivers/video/fbdev/core/fbcon.c:2620
con_font_copy drivers/tty/vt/vt.c:4594 [inline]
con_font_op+0x6b2/0x1270 drivers/tty/vt/vt.c:4609
vt_ioctl+0x181a/0x26d0 drivers/tty/vt/vt_ioctl.c:965
tty_ioctl+0xa37/0x14f0 drivers/tty/tty_io.c:2660
vfs_ioctl fs/ioctl.c:47 [inline]
file_ioctl fs/ioctl.c:545 [inline]
do_vfs_ioctl+0x977/0x14e0 fs/ioctl.c:732
ksys_ioctl+0xab/0xd0 fs/ioctl.c:749
__do_sys_ioctl fs/ioctl.c:756 [inline]
__se_sys_ioctl fs/ioctl.c:754 [inline]
__x64_sys_ioctl+0x73/0xb0 fs/ioctl.c:754
do_syscall_64+0xfa/0x790 arch/x86/entry/common.c:294
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x449c49
Code: e8 7c e6 ff ff 48 83 c4 18 c3 0f 1f 80 00 00 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 0f 83 1b 05 fc ff c3 66 2e 0f 1f 84 00 00 00 00
RSP: 002b:00007fa99f42ace8 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00000000006e6a38 RCX: 0000000000449c49
RDX: 0000000020000000 RSI: 0000000000004b72 RDI: 0000000000000004
RBP: 00000000006e6a30 R08: 00007fa99f42b700 R09: 0000000000000000
R10: 00007fa99f42b700 R11: 0000000000000246 R12: 00000000006e6a3c
R13: 00007ffe46ffe5df R14: 00007fa99f42b9c0 R15: 20c49ba5e353f7cf
The buggy address belongs to the variable:
__func__.44397+0x104/0x1c0
Memory state around the buggy address:
ffffffff8872ba00: 00 00 00 00 fa fa fa fa 00 03 fa fa fa fa fa fa
ffffffff8872ba80: 00 01 fa fa fa fa fa fa 04 fa fa fa fa fa fa fa
> ffffffff8872bb00: 04 fa fa fa fa fa fa fa 04 fa fa fa fa fa fa fa
^
ffffffff8872bb80: 04 fa fa fa fa fa fa fa 07 fa fa fa fa fa fa fa
ffffffff8872bc00: 04 fa fa fa fa fa fa fa 00 00 01 fa fa fa fa fa
==================================================================
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: KASAN: global-out-of-bounds Read in bit_putcs
@ 2019-12-18 19:21 ` syzbot
0 siblings, 0 replies; 15+ messages in thread
From: syzbot @ 2019-12-18 19:21 UTC (permalink / raw)
To: b.zolnierkie, dri-devel, linux-fbdev, linux-kernel, syzkaller-bugs
syzbot has found a reproducer for the following crash on:
HEAD commit: b9c5ef25 Add linux-next specific files for 20191218
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x\x17d57b46e00000
kernel config: https://syzkaller.appspot.com/x/.config?x.b13492323f151f
dashboard link: https://syzkaller.appspot.com/bug?extid8a3699c7eaf165b97a6
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
syz repro: https://syzkaller.appspot.com/x/repro.syz?x\x13ce1f2ee00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x\x125727dee00000
Bisection is inconclusive: the bug happens on the oldest tested release.
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x\x12caa5b6e00000
final crash: https://syzkaller.appspot.com/x/report.txt?x\x11caa5b6e00000
console output: https://syzkaller.appspot.com/x/log.txt?x\x16caa5b6e00000
IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+38a3699c7eaf165b97a6@syzkaller.appspotmail.com
=================================
BUG: KASAN: global-out-of-bounds in __fb_pad_aligned_buffer
include/linux/fb.h:654 [inline]
BUG: KASAN: global-out-of-bounds in bit_putcs_aligned
drivers/video/fbdev/core/bitblit.c:96 [inline]
BUG: KASAN: global-out-of-bounds in bit_putcs+0xd5d/0xf10
drivers/video/fbdev/core/bitblit.c:185
Read of size 1 at addr ffffffff8872bb44 by task syz-executor093/14101
CPU: 1 PID: 14101 Comm: syz-executor093 Not tainted
5.5.0-rc2-next-20191218-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+0x197/0x210 lib/dump_stack.c:118
print_address_description.constprop.0.cold+0x5/0x30b mm/kasan/report.c:374
__kasan_report.cold+0x1b/0x41 mm/kasan/report.c:506
kasan_report+0x12/0x20 mm/kasan/common.c:639
__asan_report_load1_noabort+0x14/0x20 mm/kasan/generic_report.c:132
__fb_pad_aligned_buffer include/linux/fb.h:654 [inline]
bit_putcs_aligned drivers/video/fbdev/core/bitblit.c:96 [inline]
bit_putcs+0xd5d/0xf10 drivers/video/fbdev/core/bitblit.c:185
fbcon_putcs+0x33c/0x3e0 drivers/video/fbdev/core/fbcon.c:1353
do_update_region+0x42b/0x6f0 drivers/tty/vt/vt.c:677
redraw_screen+0x676/0x7d0 drivers/tty/vt/vt.c:1011
fbcon_do_set_font+0x829/0x960 drivers/video/fbdev/core/fbcon.c:2605
fbcon_copy_font+0x12c/0x190 drivers/video/fbdev/core/fbcon.c:2620
con_font_copy drivers/tty/vt/vt.c:4594 [inline]
con_font_op+0x6b2/0x1270 drivers/tty/vt/vt.c:4609
vt_ioctl+0x181a/0x26d0 drivers/tty/vt/vt_ioctl.c:965
tty_ioctl+0xa37/0x14f0 drivers/tty/tty_io.c:2660
vfs_ioctl fs/ioctl.c:47 [inline]
file_ioctl fs/ioctl.c:545 [inline]
do_vfs_ioctl+0x977/0x14e0 fs/ioctl.c:732
ksys_ioctl+0xab/0xd0 fs/ioctl.c:749
__do_sys_ioctl fs/ioctl.c:756 [inline]
__se_sys_ioctl fs/ioctl.c:754 [inline]
__x64_sys_ioctl+0x73/0xb0 fs/ioctl.c:754
do_syscall_64+0xfa/0x790 arch/x86/entry/common.c:294
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x449c49
Code: e8 7c e6 ff ff 48 83 c4 18 c3 0f 1f 80 00 00 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 0f 83 1b 05 fc ff c3 66 2e 0f 1f 84 00 00 00 00
RSP: 002b:00007fa99f42ace8 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00000000006e6a38 RCX: 0000000000449c49
RDX: 0000000020000000 RSI: 0000000000004b72 RDI: 0000000000000004
RBP: 00000000006e6a30 R08: 00007fa99f42b700 R09: 0000000000000000
R10: 00007fa99f42b700 R11: 0000000000000246 R12: 00000000006e6a3c
R13: 00007ffe46ffe5df R14: 00007fa99f42b9c0 R15: 20c49ba5e353f7cf
The buggy address belongs to the variable:
__func__.44397+0x104/0x1c0
Memory state around the buggy address:
ffffffff8872ba00: 00 00 00 00 fa fa fa fa 00 03 fa fa fa fa fa fa
ffffffff8872ba80: 00 01 fa fa fa fa fa fa 04 fa fa fa fa fa fa fa
> ffffffff8872bb00: 04 fa fa fa fa fa fa fa 04 fa fa fa fa fa fa fa
^
ffffffff8872bb80: 04 fa fa fa fa fa fa fa 07 fa fa fa fa fa fa fa
ffffffff8872bc00: 04 fa fa fa fa fa fa fa 00 00 01 fa fa fa fa fa
=================================
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: KASAN: global-out-of-bounds Read in bit_putcs
@ 2019-12-18 19:21 ` syzbot
0 siblings, 0 replies; 15+ messages in thread
From: syzbot @ 2019-12-18 19:21 UTC (permalink / raw)
To: b.zolnierkie, dri-devel, linux-fbdev, linux-kernel, syzkaller-bugs
syzbot has found a reproducer for the following crash on:
HEAD commit: b9c5ef25 Add linux-next specific files for 20191218
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=17d57b46e00000
kernel config: https://syzkaller.appspot.com/x/.config?x=2eb13492323f151f
dashboard link: https://syzkaller.appspot.com/bug?extid=38a3699c7eaf165b97a6
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=13ce1f2ee00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=125727dee00000
Bisection is inconclusive: the bug happens on the oldest tested release.
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=12caa5b6e00000
final crash: https://syzkaller.appspot.com/x/report.txt?x=11caa5b6e00000
console output: https://syzkaller.appspot.com/x/log.txt?x=16caa5b6e00000
IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+38a3699c7eaf165b97a6@syzkaller.appspotmail.com
==================================================================
BUG: KASAN: global-out-of-bounds in __fb_pad_aligned_buffer
include/linux/fb.h:654 [inline]
BUG: KASAN: global-out-of-bounds in bit_putcs_aligned
drivers/video/fbdev/core/bitblit.c:96 [inline]
BUG: KASAN: global-out-of-bounds in bit_putcs+0xd5d/0xf10
drivers/video/fbdev/core/bitblit.c:185
Read of size 1 at addr ffffffff8872bb44 by task syz-executor093/14101
CPU: 1 PID: 14101 Comm: syz-executor093 Not tainted
5.5.0-rc2-next-20191218-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+0x197/0x210 lib/dump_stack.c:118
print_address_description.constprop.0.cold+0x5/0x30b mm/kasan/report.c:374
__kasan_report.cold+0x1b/0x41 mm/kasan/report.c:506
kasan_report+0x12/0x20 mm/kasan/common.c:639
__asan_report_load1_noabort+0x14/0x20 mm/kasan/generic_report.c:132
__fb_pad_aligned_buffer include/linux/fb.h:654 [inline]
bit_putcs_aligned drivers/video/fbdev/core/bitblit.c:96 [inline]
bit_putcs+0xd5d/0xf10 drivers/video/fbdev/core/bitblit.c:185
fbcon_putcs+0x33c/0x3e0 drivers/video/fbdev/core/fbcon.c:1353
do_update_region+0x42b/0x6f0 drivers/tty/vt/vt.c:677
redraw_screen+0x676/0x7d0 drivers/tty/vt/vt.c:1011
fbcon_do_set_font+0x829/0x960 drivers/video/fbdev/core/fbcon.c:2605
fbcon_copy_font+0x12c/0x190 drivers/video/fbdev/core/fbcon.c:2620
con_font_copy drivers/tty/vt/vt.c:4594 [inline]
con_font_op+0x6b2/0x1270 drivers/tty/vt/vt.c:4609
vt_ioctl+0x181a/0x26d0 drivers/tty/vt/vt_ioctl.c:965
tty_ioctl+0xa37/0x14f0 drivers/tty/tty_io.c:2660
vfs_ioctl fs/ioctl.c:47 [inline]
file_ioctl fs/ioctl.c:545 [inline]
do_vfs_ioctl+0x977/0x14e0 fs/ioctl.c:732
ksys_ioctl+0xab/0xd0 fs/ioctl.c:749
__do_sys_ioctl fs/ioctl.c:756 [inline]
__se_sys_ioctl fs/ioctl.c:754 [inline]
__x64_sys_ioctl+0x73/0xb0 fs/ioctl.c:754
do_syscall_64+0xfa/0x790 arch/x86/entry/common.c:294
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x449c49
Code: e8 7c e6 ff ff 48 83 c4 18 c3 0f 1f 80 00 00 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 0f 83 1b 05 fc ff c3 66 2e 0f 1f 84 00 00 00 00
RSP: 002b:00007fa99f42ace8 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00000000006e6a38 RCX: 0000000000449c49
RDX: 0000000020000000 RSI: 0000000000004b72 RDI: 0000000000000004
RBP: 00000000006e6a30 R08: 00007fa99f42b700 R09: 0000000000000000
R10: 00007fa99f42b700 R11: 0000000000000246 R12: 00000000006e6a3c
R13: 00007ffe46ffe5df R14: 00007fa99f42b9c0 R15: 20c49ba5e353f7cf
The buggy address belongs to the variable:
__func__.44397+0x104/0x1c0
Memory state around the buggy address:
ffffffff8872ba00: 00 00 00 00 fa fa fa fa 00 03 fa fa fa fa fa fa
ffffffff8872ba80: 00 01 fa fa fa fa fa fa 04 fa fa fa fa fa fa fa
> ffffffff8872bb00: 04 fa fa fa fa fa fa fa 04 fa fa fa fa fa fa fa
^
ffffffff8872bb80: 04 fa fa fa fa fa fa fa 07 fa fa fa fa fa fa fa
ffffffff8872bc00: 04 fa fa fa fa fa fa fa 00 00 01 fa fa fa fa fa
==================================================================
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
^ permalink raw reply [flat|nested] 15+ messages in thread
* KASAN: global-out-of-bounds Read in bit_putcs (2)
2019-12-05 16:46 ` syzbot
(?)
@ 2020-09-26 7:19 ` syzbot
-1 siblings, 0 replies; 15+ messages in thread
From: syzbot @ 2020-09-26 7:19 UTC (permalink / raw)
To: b.zolnierkie, daniel.vetter, deller, dri-devel, gregkh,
jirislaby, linux-fbdev, linux-kernel, penguin-kernel,
syzkaller-bugs
Hello,
syzbot found the following issue on:
HEAD commit: 171d4ff7 Merge tag 'mmc-v5.9-rc4-2' of git://git.kernel.or..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=126e918d900000
kernel config: https://syzkaller.appspot.com/x/.config?x=240e2ebab67245c7
dashboard link: https://syzkaller.appspot.com/bug?extid=a889d70ef11d6e0f6f22
compiler: gcc (GCC) 10.1.0-syz 20200507
Unfortunately, I don't have any reproducer for this issue yet.
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+a889d70ef11d6e0f6f22@syzkaller.appspotmail.com
==================================================================
BUG: KASAN: global-out-of-bounds in __fb_pad_aligned_buffer include/linux/fb.h:654 [inline]
BUG: KASAN: global-out-of-bounds in bit_putcs_aligned drivers/video/fbdev/core/bitblit.c:96 [inline]
BUG: KASAN: global-out-of-bounds in bit_putcs+0xbb6/0xd20 drivers/video/fbdev/core/bitblit.c:185
Read of size 1 at addr ffffffff88db78e9 by task syz-executor.4/16465
CPU: 0 PID: 16465 Comm: syz-executor.4 Not tainted 5.9.0-rc6-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+0x198/0x1fd lib/dump_stack.c:118
print_address_description.constprop.0.cold+0x5/0x497 mm/kasan/report.c:383
__kasan_report mm/kasan/report.c:513 [inline]
kasan_report.cold+0x1f/0x37 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+0xbb6/0xd20 drivers/video/fbdev/core/bitblit.c:185
fbcon_putcs+0x35a/0x450 drivers/video/fbdev/core/fbcon.c:1308
do_update_region+0x399/0x630 drivers/tty/vt/vt.c:675
redraw_screen+0x658/0x790 drivers/tty/vt/vt.c:1034
fbcon_do_set_font+0x718/0x880 drivers/video/fbdev/core/fbcon.c:2438
fbcon_copy_font+0x12f/0x1a0 drivers/video/fbdev/core/fbcon.c:2453
con_font_copy drivers/tty/vt/vt.c:4719 [inline]
con_font_op+0x65b/0x1140 drivers/tty/vt/vt.c:4734
vt_k_ioctl drivers/tty/vt/vt_ioctl.c:473 [inline]
vt_ioctl+0x21c9/0x2e90 drivers/tty/vt/vt_ioctl.c:852
tty_ioctl+0x1019/0x15f0 drivers/tty/tty_io.c:2656
vfs_ioctl fs/ioctl.c:48 [inline]
__do_sys_ioctl fs/ioctl.c:753 [inline]
__se_sys_ioctl fs/ioctl.c:739 [inline]
__x64_sys_ioctl+0x193/0x200 fs/ioctl.c:739
do_syscall_64+0x2d/0x70 arch/x86/entry/common.c:46
entry_SYSCALL_64_after_hwframe+0x44/0xa9
RIP: 0033:0x45e179
Code: 3d b2 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 0b b2 fb ff c3 66 2e 0f 1f 84 00 00 00 00
RSP: 002b:00007fe2e03e5c78 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 0000000000010840 RCX: 000000000045e179
RDX: 0000000020000400 RSI: 0000000000004b72 RDI: 0000000000000003
RBP: 000000000118cf80 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 000000000118cf4c
R13: 00007ffff7397e9f R14: 00007fe2e03e69c0 R15: 000000000118cf4c
The buggy address belongs to the variable:
oid_index+0x109/0xae0
Memory state around the buggy address:
ffffffff88db7780: 00 00 00 00 01 f9 f9 f9 f9 f9 f9 f9 00 00 00 00
ffffffff88db7800: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 06 f9
>ffffffff88db7880: f9 f9 f9 f9 00 02 f9 f9 f9 f9 f9 f9 00 01 f9 f9
^
ffffffff88db7900: f9 f9 f9 f9 00 04 f9 f9 f9 f9 f9 f9 00 00 02 f9
ffffffff88db7980: f9 f9 f9 f9 00 03 f9 f9 f9 f9 f9 f9 07 f9 f9 f9
==================================================================
---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzkaller@googlegroups.com.
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
^ permalink raw reply [flat|nested] 15+ messages in thread
* KASAN: global-out-of-bounds Read in bit_putcs (2)
@ 2020-09-26 7:19 ` syzbot
0 siblings, 0 replies; 15+ messages in thread
From: syzbot @ 2020-09-26 7:19 UTC (permalink / raw)
To: b.zolnierkie, daniel.vetter, deller, dri-devel, gregkh,
jirislaby, linux-fbdev, linux-kernel, penguin-kernel,
syzkaller-bugs
Hello,
syzbot found the following issue on:
HEAD commit: 171d4ff7 Merge tag 'mmc-v5.9-rc4-2' of git://git.kernel.or..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x\x126e918d900000
kernel config: https://syzkaller.appspot.com/x/.config?x$0e2ebab67245c7
dashboard link: https://syzkaller.appspot.com/bug?extid¨89d70ef11d6e0f6f22
compiler: gcc (GCC) 10.1.0-syz 20200507
Unfortunately, I don't have any reproducer for this issue yet.
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+a889d70ef11d6e0f6f22@syzkaller.appspotmail.com
=================================
BUG: KASAN: global-out-of-bounds in __fb_pad_aligned_buffer include/linux/fb.h:654 [inline]
BUG: KASAN: global-out-of-bounds in bit_putcs_aligned drivers/video/fbdev/core/bitblit.c:96 [inline]
BUG: KASAN: global-out-of-bounds in bit_putcs+0xbb6/0xd20 drivers/video/fbdev/core/bitblit.c:185
Read of size 1 at addr ffffffff88db78e9 by task syz-executor.4/16465
CPU: 0 PID: 16465 Comm: syz-executor.4 Not tainted 5.9.0-rc6-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+0x198/0x1fd lib/dump_stack.c:118
print_address_description.constprop.0.cold+0x5/0x497 mm/kasan/report.c:383
__kasan_report mm/kasan/report.c:513 [inline]
kasan_report.cold+0x1f/0x37 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+0xbb6/0xd20 drivers/video/fbdev/core/bitblit.c:185
fbcon_putcs+0x35a/0x450 drivers/video/fbdev/core/fbcon.c:1308
do_update_region+0x399/0x630 drivers/tty/vt/vt.c:675
redraw_screen+0x658/0x790 drivers/tty/vt/vt.c:1034
fbcon_do_set_font+0x718/0x880 drivers/video/fbdev/core/fbcon.c:2438
fbcon_copy_font+0x12f/0x1a0 drivers/video/fbdev/core/fbcon.c:2453
con_font_copy drivers/tty/vt/vt.c:4719 [inline]
con_font_op+0x65b/0x1140 drivers/tty/vt/vt.c:4734
vt_k_ioctl drivers/tty/vt/vt_ioctl.c:473 [inline]
vt_ioctl+0x21c9/0x2e90 drivers/tty/vt/vt_ioctl.c:852
tty_ioctl+0x1019/0x15f0 drivers/tty/tty_io.c:2656
vfs_ioctl fs/ioctl.c:48 [inline]
__do_sys_ioctl fs/ioctl.c:753 [inline]
__se_sys_ioctl fs/ioctl.c:739 [inline]
__x64_sys_ioctl+0x193/0x200 fs/ioctl.c:739
do_syscall_64+0x2d/0x70 arch/x86/entry/common.c:46
entry_SYSCALL_64_after_hwframe+0x44/0xa9
RIP: 0033:0x45e179
Code: 3d b2 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 0b b2 fb ff c3 66 2e 0f 1f 84 00 00 00 00
RSP: 002b:00007fe2e03e5c78 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 0000000000010840 RCX: 000000000045e179
RDX: 0000000020000400 RSI: 0000000000004b72 RDI: 0000000000000003
RBP: 000000000118cf80 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 000000000118cf4c
R13: 00007ffff7397e9f R14: 00007fe2e03e69c0 R15: 000000000118cf4c
The buggy address belongs to the variable:
oid_index+0x109/0xae0
Memory state around the buggy address:
ffffffff88db7780: 00 00 00 00 01 f9 f9 f9 f9 f9 f9 f9 00 00 00 00
ffffffff88db7800: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 06 f9
>ffffffff88db7880: f9 f9 f9 f9 00 02 f9 f9 f9 f9 f9 f9 00 01 f9 f9
^
ffffffff88db7900: f9 f9 f9 f9 00 04 f9 f9 f9 f9 f9 f9 00 00 02 f9
ffffffff88db7980: f9 f9 f9 f9 00 03 f9 f9 f9 f9 f9 f9 07 f9 f9 f9
=================================
---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzkaller@googlegroups.com.
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
^ permalink raw reply [flat|nested] 15+ messages in thread
* KASAN: global-out-of-bounds Read in bit_putcs (2)
@ 2020-09-26 7:19 ` syzbot
0 siblings, 0 replies; 15+ messages in thread
From: syzbot @ 2020-09-26 7:19 UTC (permalink / raw)
To: b.zolnierkie, daniel.vetter, deller, dri-devel, gregkh,
jirislaby, linux-fbdev, linux-kernel, penguin-kernel,
syzkaller-bugs
Hello,
syzbot found the following issue on:
HEAD commit: 171d4ff7 Merge tag 'mmc-v5.9-rc4-2' of git://git.kernel.or..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=126e918d900000
kernel config: https://syzkaller.appspot.com/x/.config?x=240e2ebab67245c7
dashboard link: https://syzkaller.appspot.com/bug?extid=a889d70ef11d6e0f6f22
compiler: gcc (GCC) 10.1.0-syz 20200507
Unfortunately, I don't have any reproducer for this issue yet.
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+a889d70ef11d6e0f6f22@syzkaller.appspotmail.com
==================================================================
BUG: KASAN: global-out-of-bounds in __fb_pad_aligned_buffer include/linux/fb.h:654 [inline]
BUG: KASAN: global-out-of-bounds in bit_putcs_aligned drivers/video/fbdev/core/bitblit.c:96 [inline]
BUG: KASAN: global-out-of-bounds in bit_putcs+0xbb6/0xd20 drivers/video/fbdev/core/bitblit.c:185
Read of size 1 at addr ffffffff88db78e9 by task syz-executor.4/16465
CPU: 0 PID: 16465 Comm: syz-executor.4 Not tainted 5.9.0-rc6-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+0x198/0x1fd lib/dump_stack.c:118
print_address_description.constprop.0.cold+0x5/0x497 mm/kasan/report.c:383
__kasan_report mm/kasan/report.c:513 [inline]
kasan_report.cold+0x1f/0x37 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+0xbb6/0xd20 drivers/video/fbdev/core/bitblit.c:185
fbcon_putcs+0x35a/0x450 drivers/video/fbdev/core/fbcon.c:1308
do_update_region+0x399/0x630 drivers/tty/vt/vt.c:675
redraw_screen+0x658/0x790 drivers/tty/vt/vt.c:1034
fbcon_do_set_font+0x718/0x880 drivers/video/fbdev/core/fbcon.c:2438
fbcon_copy_font+0x12f/0x1a0 drivers/video/fbdev/core/fbcon.c:2453
con_font_copy drivers/tty/vt/vt.c:4719 [inline]
con_font_op+0x65b/0x1140 drivers/tty/vt/vt.c:4734
vt_k_ioctl drivers/tty/vt/vt_ioctl.c:473 [inline]
vt_ioctl+0x21c9/0x2e90 drivers/tty/vt/vt_ioctl.c:852
tty_ioctl+0x1019/0x15f0 drivers/tty/tty_io.c:2656
vfs_ioctl fs/ioctl.c:48 [inline]
__do_sys_ioctl fs/ioctl.c:753 [inline]
__se_sys_ioctl fs/ioctl.c:739 [inline]
__x64_sys_ioctl+0x193/0x200 fs/ioctl.c:739
do_syscall_64+0x2d/0x70 arch/x86/entry/common.c:46
entry_SYSCALL_64_after_hwframe+0x44/0xa9
RIP: 0033:0x45e179
Code: 3d b2 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 0b b2 fb ff c3 66 2e 0f 1f 84 00 00 00 00
RSP: 002b:00007fe2e03e5c78 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 0000000000010840 RCX: 000000000045e179
RDX: 0000000020000400 RSI: 0000000000004b72 RDI: 0000000000000003
RBP: 000000000118cf80 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 000000000118cf4c
R13: 00007ffff7397e9f R14: 00007fe2e03e69c0 R15: 000000000118cf4c
The buggy address belongs to the variable:
oid_index+0x109/0xae0
Memory state around the buggy address:
ffffffff88db7780: 00 00 00 00 01 f9 f9 f9 f9 f9 f9 f9 00 00 00 00
ffffffff88db7800: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 06 f9
>ffffffff88db7880: f9 f9 f9 f9 00 02 f9 f9 f9 f9 f9 f9 00 01 f9 f9
^
ffffffff88db7900: f9 f9 f9 f9 00 04 f9 f9 f9 f9 f9 f9 00 00 02 f9
ffffffff88db7980: f9 f9 f9 f9 00 03 f9 f9 f9 f9 f9 f9 07 f9 f9 f9
==================================================================
---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzkaller@googlegroups.com.
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: KASAN: global-out-of-bounds Read in bit_putcs (2)
2020-09-26 7:19 ` syzbot
(?)
@ 2020-09-26 15:55 ` Daniel Vetter
-1 siblings, 0 replies; 15+ messages in thread
From: Daniel Vetter @ 2020-09-26 15:55 UTC (permalink / raw)
To: syzbot
Cc: Bartlomiej Zolnierkiewicz, Helge Deller, dri-devel, Greg KH,
Jiri Slaby, Linux Fbdev development list,
Linux Kernel Mailing List, Tetsuo Handa, syzkaller-bugs
On Sat, Sep 26, 2020 at 9:19 AM syzbot
<syzbot+a889d70ef11d6e0f6f22@syzkaller.appspotmail.com> wrote:
>
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: 171d4ff7 Merge tag 'mmc-v5.9-rc4-2' of git://git.kernel.or..
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=126e918d900000
> kernel config: https://syzkaller.appspot.com/x/.config?x=240e2ebab67245c7
> dashboard link: https://syzkaller.appspot.com/bug?extid=a889d70ef11d6e0f6f22
> compiler: gcc (GCC) 10.1.0-syz 20200507
>
> Unfortunately, I don't have any reproducer for this issue yet.
Looking at the backtrace, this could be fixed by the font size checks
I just pushed:
commit 5af08640795b2b9a940c9266c0260455377ae262 (HEAD ->
drm-misc-fixes, drm-misc/for-linux-next-fixes,
drm-misc/drm-misc-fixes)
Author: Peilin Ye <yepeilin.cs@gmail.com>
Date: Thu Sep 24 09:43:48 2020 -0400
fbcon: Fix global-out-of-bounds read in fbcon_get_font()
But just an educated guess, no more.
-Daniel
>
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: syzbot+a889d70ef11d6e0f6f22@syzkaller.appspotmail.com
>
> ==================================================================
> BUG: KASAN: global-out-of-bounds in __fb_pad_aligned_buffer include/linux/fb.h:654 [inline]
> BUG: KASAN: global-out-of-bounds in bit_putcs_aligned drivers/video/fbdev/core/bitblit.c:96 [inline]
> BUG: KASAN: global-out-of-bounds in bit_putcs+0xbb6/0xd20 drivers/video/fbdev/core/bitblit.c:185
> Read of size 1 at addr ffffffff88db78e9 by task syz-executor.4/16465
>
> CPU: 0 PID: 16465 Comm: syz-executor.4 Not tainted 5.9.0-rc6-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+0x198/0x1fd lib/dump_stack.c:118
> print_address_description.constprop.0.cold+0x5/0x497 mm/kasan/report.c:383
> __kasan_report mm/kasan/report.c:513 [inline]
> kasan_report.cold+0x1f/0x37 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+0xbb6/0xd20 drivers/video/fbdev/core/bitblit.c:185
> fbcon_putcs+0x35a/0x450 drivers/video/fbdev/core/fbcon.c:1308
> do_update_region+0x399/0x630 drivers/tty/vt/vt.c:675
> redraw_screen+0x658/0x790 drivers/tty/vt/vt.c:1034
> fbcon_do_set_font+0x718/0x880 drivers/video/fbdev/core/fbcon.c:2438
> fbcon_copy_font+0x12f/0x1a0 drivers/video/fbdev/core/fbcon.c:2453
> con_font_copy drivers/tty/vt/vt.c:4719 [inline]
> con_font_op+0x65b/0x1140 drivers/tty/vt/vt.c:4734
> vt_k_ioctl drivers/tty/vt/vt_ioctl.c:473 [inline]
> vt_ioctl+0x21c9/0x2e90 drivers/tty/vt/vt_ioctl.c:852
> tty_ioctl+0x1019/0x15f0 drivers/tty/tty_io.c:2656
> vfs_ioctl fs/ioctl.c:48 [inline]
> __do_sys_ioctl fs/ioctl.c:753 [inline]
> __se_sys_ioctl fs/ioctl.c:739 [inline]
> __x64_sys_ioctl+0x193/0x200 fs/ioctl.c:739
> do_syscall_64+0x2d/0x70 arch/x86/entry/common.c:46
> entry_SYSCALL_64_after_hwframe+0x44/0xa9
> RIP: 0033:0x45e179
> Code: 3d b2 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 0b b2 fb ff c3 66 2e 0f 1f 84 00 00 00 00
> RSP: 002b:00007fe2e03e5c78 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
> RAX: ffffffffffffffda RBX: 0000000000010840 RCX: 000000000045e179
> RDX: 0000000020000400 RSI: 0000000000004b72 RDI: 0000000000000003
> RBP: 000000000118cf80 R08: 0000000000000000 R09: 0000000000000000
> R10: 0000000000000000 R11: 0000000000000246 R12: 000000000118cf4c
> R13: 00007ffff7397e9f R14: 00007fe2e03e69c0 R15: 000000000118cf4c
>
> The buggy address belongs to the variable:
> oid_index+0x109/0xae0
>
> Memory state around the buggy address:
> ffffffff88db7780: 00 00 00 00 01 f9 f9 f9 f9 f9 f9 f9 00 00 00 00
> ffffffff88db7800: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 06 f9
> >ffffffff88db7880: f9 f9 f9 f9 00 02 f9 f9 f9 f9 f9 f9 00 01 f9 f9
> ^
> ffffffff88db7900: f9 f9 f9 f9 00 04 f9 f9 f9 f9 f9 f9 00 00 02 f9
> ffffffff88db7980: f9 f9 f9 f9 00 03 f9 f9 f9 f9 f9 f9 07 f9 f9 f9
> ==================================================================
>
>
> ---
> This report is generated by a bot. It may contain errors.
> See https://goo.gl/tpsmEJ for more information about syzbot.
> syzbot engineers can be reached at syzkaller@googlegroups.com.
>
> syzbot will keep track of this issue. See:
> https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: KASAN: global-out-of-bounds Read in bit_putcs (2)
@ 2020-09-26 15:55 ` Daniel Vetter
0 siblings, 0 replies; 15+ messages in thread
From: Daniel Vetter @ 2020-09-26 15:55 UTC (permalink / raw)
To: syzbot
Cc: Linux Fbdev development list, Bartlomiej Zolnierkiewicz,
Tetsuo Handa, Greg KH, Helge Deller, syzkaller-bugs,
Linux Kernel Mailing List, dri-devel, Jiri Slaby
On Sat, Sep 26, 2020 at 9:19 AM syzbot
<syzbot+a889d70ef11d6e0f6f22@syzkaller.appspotmail.com> wrote:
>
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: 171d4ff7 Merge tag 'mmc-v5.9-rc4-2' of git://git.kernel.or..
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x\x126e918d900000
> kernel config: https://syzkaller.appspot.com/x/.config?x$0e2ebab67245c7
> dashboard link: https://syzkaller.appspot.com/bug?extid¨89d70ef11d6e0f6f22
> compiler: gcc (GCC) 10.1.0-syz 20200507
>
> Unfortunately, I don't have any reproducer for this issue yet.
Looking at the backtrace, this could be fixed by the font size checks
I just pushed:
commit 5af08640795b2b9a940c9266c0260455377ae262 (HEAD ->
drm-misc-fixes, drm-misc/for-linux-next-fixes,
drm-misc/drm-misc-fixes)
Author: Peilin Ye <yepeilin.cs@gmail.com>
Date: Thu Sep 24 09:43:48 2020 -0400
fbcon: Fix global-out-of-bounds read in fbcon_get_font()
But just an educated guess, no more.
-Daniel
>
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: syzbot+a889d70ef11d6e0f6f22@syzkaller.appspotmail.com
>
> =================================
> BUG: KASAN: global-out-of-bounds in __fb_pad_aligned_buffer include/linux/fb.h:654 [inline]
> BUG: KASAN: global-out-of-bounds in bit_putcs_aligned drivers/video/fbdev/core/bitblit.c:96 [inline]
> BUG: KASAN: global-out-of-bounds in bit_putcs+0xbb6/0xd20 drivers/video/fbdev/core/bitblit.c:185
> Read of size 1 at addr ffffffff88db78e9 by task syz-executor.4/16465
>
> CPU: 0 PID: 16465 Comm: syz-executor.4 Not tainted 5.9.0-rc6-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+0x198/0x1fd lib/dump_stack.c:118
> print_address_description.constprop.0.cold+0x5/0x497 mm/kasan/report.c:383
> __kasan_report mm/kasan/report.c:513 [inline]
> kasan_report.cold+0x1f/0x37 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+0xbb6/0xd20 drivers/video/fbdev/core/bitblit.c:185
> fbcon_putcs+0x35a/0x450 drivers/video/fbdev/core/fbcon.c:1308
> do_update_region+0x399/0x630 drivers/tty/vt/vt.c:675
> redraw_screen+0x658/0x790 drivers/tty/vt/vt.c:1034
> fbcon_do_set_font+0x718/0x880 drivers/video/fbdev/core/fbcon.c:2438
> fbcon_copy_font+0x12f/0x1a0 drivers/video/fbdev/core/fbcon.c:2453
> con_font_copy drivers/tty/vt/vt.c:4719 [inline]
> con_font_op+0x65b/0x1140 drivers/tty/vt/vt.c:4734
> vt_k_ioctl drivers/tty/vt/vt_ioctl.c:473 [inline]
> vt_ioctl+0x21c9/0x2e90 drivers/tty/vt/vt_ioctl.c:852
> tty_ioctl+0x1019/0x15f0 drivers/tty/tty_io.c:2656
> vfs_ioctl fs/ioctl.c:48 [inline]
> __do_sys_ioctl fs/ioctl.c:753 [inline]
> __se_sys_ioctl fs/ioctl.c:739 [inline]
> __x64_sys_ioctl+0x193/0x200 fs/ioctl.c:739
> do_syscall_64+0x2d/0x70 arch/x86/entry/common.c:46
> entry_SYSCALL_64_after_hwframe+0x44/0xa9
> RIP: 0033:0x45e179
> Code: 3d b2 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 0b b2 fb ff c3 66 2e 0f 1f 84 00 00 00 00
> RSP: 002b:00007fe2e03e5c78 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
> RAX: ffffffffffffffda RBX: 0000000000010840 RCX: 000000000045e179
> RDX: 0000000020000400 RSI: 0000000000004b72 RDI: 0000000000000003
> RBP: 000000000118cf80 R08: 0000000000000000 R09: 0000000000000000
> R10: 0000000000000000 R11: 0000000000000246 R12: 000000000118cf4c
> R13: 00007ffff7397e9f R14: 00007fe2e03e69c0 R15: 000000000118cf4c
>
> The buggy address belongs to the variable:
> oid_index+0x109/0xae0
>
> Memory state around the buggy address:
> ffffffff88db7780: 00 00 00 00 01 f9 f9 f9 f9 f9 f9 f9 00 00 00 00
> ffffffff88db7800: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 06 f9
> >ffffffff88db7880: f9 f9 f9 f9 00 02 f9 f9 f9 f9 f9 f9 00 01 f9 f9
> ^
> ffffffff88db7900: f9 f9 f9 f9 00 04 f9 f9 f9 f9 f9 f9 00 00 02 f9
> ffffffff88db7980: f9 f9 f9 f9 00 03 f9 f9 f9 f9 f9 f9 07 f9 f9 f9
> =================================
>
>
> ---
> This report is generated by a bot. It may contain errors.
> See https://goo.gl/tpsmEJ for more information about syzbot.
> syzbot engineers can be reached at syzkaller@googlegroups.com.
>
> syzbot will keep track of this issue. See:
> https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: KASAN: global-out-of-bounds Read in bit_putcs (2)
@ 2020-09-26 15:55 ` Daniel Vetter
0 siblings, 0 replies; 15+ messages in thread
From: Daniel Vetter @ 2020-09-26 15:55 UTC (permalink / raw)
To: syzbot
Cc: Linux Fbdev development list, Bartlomiej Zolnierkiewicz,
Tetsuo Handa, Greg KH, Helge Deller, syzkaller-bugs,
Linux Kernel Mailing List, dri-devel, Jiri Slaby
On Sat, Sep 26, 2020 at 9:19 AM syzbot
<syzbot+a889d70ef11d6e0f6f22@syzkaller.appspotmail.com> wrote:
>
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: 171d4ff7 Merge tag 'mmc-v5.9-rc4-2' of git://git.kernel.or..
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=126e918d900000
> kernel config: https://syzkaller.appspot.com/x/.config?x=240e2ebab67245c7
> dashboard link: https://syzkaller.appspot.com/bug?extid=a889d70ef11d6e0f6f22
> compiler: gcc (GCC) 10.1.0-syz 20200507
>
> Unfortunately, I don't have any reproducer for this issue yet.
Looking at the backtrace, this could be fixed by the font size checks
I just pushed:
commit 5af08640795b2b9a940c9266c0260455377ae262 (HEAD ->
drm-misc-fixes, drm-misc/for-linux-next-fixes,
drm-misc/drm-misc-fixes)
Author: Peilin Ye <yepeilin.cs@gmail.com>
Date: Thu Sep 24 09:43:48 2020 -0400
fbcon: Fix global-out-of-bounds read in fbcon_get_font()
But just an educated guess, no more.
-Daniel
>
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: syzbot+a889d70ef11d6e0f6f22@syzkaller.appspotmail.com
>
> ==================================================================
> BUG: KASAN: global-out-of-bounds in __fb_pad_aligned_buffer include/linux/fb.h:654 [inline]
> BUG: KASAN: global-out-of-bounds in bit_putcs_aligned drivers/video/fbdev/core/bitblit.c:96 [inline]
> BUG: KASAN: global-out-of-bounds in bit_putcs+0xbb6/0xd20 drivers/video/fbdev/core/bitblit.c:185
> Read of size 1 at addr ffffffff88db78e9 by task syz-executor.4/16465
>
> CPU: 0 PID: 16465 Comm: syz-executor.4 Not tainted 5.9.0-rc6-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+0x198/0x1fd lib/dump_stack.c:118
> print_address_description.constprop.0.cold+0x5/0x497 mm/kasan/report.c:383
> __kasan_report mm/kasan/report.c:513 [inline]
> kasan_report.cold+0x1f/0x37 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+0xbb6/0xd20 drivers/video/fbdev/core/bitblit.c:185
> fbcon_putcs+0x35a/0x450 drivers/video/fbdev/core/fbcon.c:1308
> do_update_region+0x399/0x630 drivers/tty/vt/vt.c:675
> redraw_screen+0x658/0x790 drivers/tty/vt/vt.c:1034
> fbcon_do_set_font+0x718/0x880 drivers/video/fbdev/core/fbcon.c:2438
> fbcon_copy_font+0x12f/0x1a0 drivers/video/fbdev/core/fbcon.c:2453
> con_font_copy drivers/tty/vt/vt.c:4719 [inline]
> con_font_op+0x65b/0x1140 drivers/tty/vt/vt.c:4734
> vt_k_ioctl drivers/tty/vt/vt_ioctl.c:473 [inline]
> vt_ioctl+0x21c9/0x2e90 drivers/tty/vt/vt_ioctl.c:852
> tty_ioctl+0x1019/0x15f0 drivers/tty/tty_io.c:2656
> vfs_ioctl fs/ioctl.c:48 [inline]
> __do_sys_ioctl fs/ioctl.c:753 [inline]
> __se_sys_ioctl fs/ioctl.c:739 [inline]
> __x64_sys_ioctl+0x193/0x200 fs/ioctl.c:739
> do_syscall_64+0x2d/0x70 arch/x86/entry/common.c:46
> entry_SYSCALL_64_after_hwframe+0x44/0xa9
> RIP: 0033:0x45e179
> Code: 3d b2 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 0b b2 fb ff c3 66 2e 0f 1f 84 00 00 00 00
> RSP: 002b:00007fe2e03e5c78 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
> RAX: ffffffffffffffda RBX: 0000000000010840 RCX: 000000000045e179
> RDX: 0000000020000400 RSI: 0000000000004b72 RDI: 0000000000000003
> RBP: 000000000118cf80 R08: 0000000000000000 R09: 0000000000000000
> R10: 0000000000000000 R11: 0000000000000246 R12: 000000000118cf4c
> R13: 00007ffff7397e9f R14: 00007fe2e03e69c0 R15: 000000000118cf4c
>
> The buggy address belongs to the variable:
> oid_index+0x109/0xae0
>
> Memory state around the buggy address:
> ffffffff88db7780: 00 00 00 00 01 f9 f9 f9 f9 f9 f9 f9 00 00 00 00
> ffffffff88db7800: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 06 f9
> >ffffffff88db7880: f9 f9 f9 f9 00 02 f9 f9 f9 f9 f9 f9 00 01 f9 f9
> ^
> ffffffff88db7900: f9 f9 f9 f9 00 04 f9 f9 f9 f9 f9 f9 00 00 02 f9
> ffffffff88db7980: f9 f9 f9 f9 00 03 f9 f9 f9 f9 f9 f9 07 f9 f9 f9
> ==================================================================
>
>
> ---
> This report is generated by a bot. It may contain errors.
> See https://goo.gl/tpsmEJ for more information about syzbot.
> syzbot engineers can be reached at syzkaller@googlegroups.com.
>
> syzbot will keep track of this issue. See:
> https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
^ permalink raw reply [flat|nested] 15+ messages in thread
end of thread, other threads:[~2020-09-28 7:08 UTC | newest]
Thread overview: 15+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-12-05 16:46 KASAN: global-out-of-bounds Read in bit_putcs syzbot
2019-12-05 16:46 ` syzbot
2019-12-05 16:46 ` syzbot
2019-12-06 16:34 ` syzbot
2019-12-06 16:34 ` syzbot
2019-12-06 16:34 ` syzbot
2019-12-18 19:21 ` syzbot
2019-12-18 19:21 ` syzbot
2019-12-18 19:21 ` syzbot
2020-09-26 7:19 KASAN: global-out-of-bounds Read in bit_putcs (2) syzbot
2020-09-26 7:19 ` syzbot
2020-09-26 7:19 ` syzbot
2020-09-26 15:55 ` Daniel Vetter
2020-09-26 15:55 ` Daniel Vetter
2020-09-26 15:55 ` Daniel Vetter
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.