general protection fault in fbcon_cursor

20 views
Skip to first unread message

syzbot

unread,
Jan 23, 2020, 9:58:10 PM1/23/20
to syzkaller...@googlegroups.com
Hello,

syzbot found the following crash on:

HEAD commit: 8bac5040 Linux 4.14.167
git tree: linux-4.14.y
console output: https://syzkaller.appspot.com/x/log.txt?x=16b82f21e00000
kernel config: https://syzkaller.appspot.com/x/.config?x=ed52db44a31a52da
dashboard link: https://syzkaller.appspot.com/bug?extid=cbd4da6bc76fd38f68b5
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+cbd4da...@syzkaller.appspotmail.com

kasan: CONFIG_KASAN_INLINE enabled
kasan: GPF could be caused by NULL-ptr deref or user memory access
general protection fault: 0000 [#1] PREEMPT SMP KASAN
Modules linked in:
CPU: 1 PID: 23 Comm: kworker/1:1 Not tainted 4.14.167-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Workqueue: events console_callback
task: ffff8880a9eca600 task.stack: ffff8880a9ed0000
RIP: 0010:fbcon_cursor+0x114/0x6f0 drivers/video/fbdev/core/fbcon.c:1325
RSP: 0018:ffff8880a9ed7b48 EFLAGS: 00010206
RAX: dffffc0000000000 RBX: ffff8880a5f6c040 RCX: ffff8880a15c99b4
RDX: 000000001fffffff RSI: 0000000000000001 RDI: ffff8880a15c9a20
RBP: ffff8880a9ed7b88 R08: ffff8882192bf270 R09: ffffed1014beed2c
R10: ffffed1014beed2b R11: ffff8880a5f7695f R12: ffff8880a15c9680
R13: ffff8882192bee00 R14: 0000000000000001 R15: 00000000fffffff8
FS: 0000000000000000(0000) GS:ffff8880aed00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00000000007d27c8 CR3: 000000008895a000 CR4: 00000000001426e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
set_cursor drivers/tty/vt/vt.c:602 [inline]
set_cursor+0x1bd/0x240 drivers/tty/vt/vt.c:593
redraw_screen+0x596/0x7c0 drivers/tty/vt/vt.c:706
complete_change_console+0xfe/0x360 drivers/tty/vt/vt_ioctl.c:1291
change_console+0x161/0x270 drivers/tty/vt/vt_ioctl.c:1416
console_callback+0x337/0x390 drivers/tty/vt/vt.c:2460
process_one_work+0x863/0x1600 kernel/workqueue.c:2114
worker_thread+0x5d9/0x1050 kernel/workqueue.c:2248
kthread+0x319/0x430 kernel/kthread.c:232
ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:404
Code: df 48 89 fa 48 c1 ea 03 80 3c 02 00 0f 85 83 05 00 00 4d 8b bc 24 a0 03 00 00 48 b8 00 00 00 00 00 fc ff df 4c 89 fa 48 c1 ea 03 <0f> b6 14 02 4c 89 f8 83 e0 07 83 c0 01 38 d0 7c 08 84 d2 0f 85
RIP: fbcon_cursor+0x114/0x6f0 drivers/video/fbdev/core/fbcon.c:1325 RSP: ffff8880a9ed7b48
---[ end trace adaa7eea101ae8e5 ]---


---
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 syzk...@googlegroups.com.

syzbot will keep track of this bug report. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

syzbot

unread,
Feb 11, 2020, 11:31:11 PM2/11/20
to syzkaller...@googlegroups.com
syzbot has found a reproducer for the following crash on:

HEAD commit: e0f8b8a6 Linux 4.14.170
git tree: linux-4.14.y
console output: https://syzkaller.appspot.com/x/log.txt?x=14b2dc29e00000
kernel config: https://syzkaller.appspot.com/x/.config?x=633dd9db249084f5
dashboard link: https://syzkaller.appspot.com/bug?extid=cbd4da6bc76fd38f68b5
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1263b395e00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1674bfa5e00000

IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+cbd4da...@syzkaller.appspotmail.com

audit: type=1400 audit(1581481633.777:36): avc: denied { map } for pid=7391 comm="syz-executor160" path="/root/syz-executor160516488" dev="sda1" ino=16483 scontext=unconfined_u:system_r:insmod_t:s0-s0:c0.c1023 tcontext=unconfined_u:object_r:user_home_t:s0 tclass=file permissive=1
kasan: CONFIG_KASAN_INLINE enabled
kasan: GPF could be caused by NULL-ptr deref or user memory access
general protection fault: 0000 [#1] PREEMPT SMP KASAN
Modules linked in:
CPU: 1 PID: 2734 Comm: kworker/1:2 Not tainted 4.14.170-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Workqueue: events console_callback
task: ffff88809f4ba4c0 task.stack: ffff88809f4c8000
RIP: 0010:fbcon_cursor+0x114/0x6f0 drivers/video/fbdev/core/fbcon.c:1325
RSP: 0018:ffff88809f4cfb48 EFLAGS: 00010203
RAX: dffffc0000000000 RBX: ffff8880a5caa540 RCX: ffff888097e519f4
RDX: 0000000020000001 RSI: 0000000000000001 RDI: ffff888097e51a60
RBP: ffff88809f4cfb88 R08: ffff8882192f8a30 R09: ffffed1043256094
R10: ffffed1043256093 R11: ffff8882192b049f R12: ffff888097e516c0
R13: ffff8882192f85c0 R14: 0000000000000001 R15: 000000010000000c
FS: 0000000000000000(0000) GS:ffff8880aed00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fdc7c5cb000 CR3: 00000000a937f000 CR4: 00000000001406e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
set_cursor drivers/tty/vt/vt.c:602 [inline]
set_cursor+0x1bd/0x240 drivers/tty/vt/vt.c:593
redraw_screen+0x596/0x7c0 drivers/tty/vt/vt.c:706
complete_change_console+0xfe/0x360 drivers/tty/vt/vt_ioctl.c:1291
change_console+0x161/0x270 drivers/tty/vt/vt_ioctl.c:1416
console_callback+0x337/0x390 drivers/tty/vt/vt.c:2460
process_one_work+0x863/0x1600 kernel/workqueue.c:2114
worker_thread+0x5d9/0x1050 kernel/workqueue.c:2248
kthread+0x319/0x430 kernel/kthread.c:232
ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:404
Code: df 48 89 fa 48 c1 ea 03 80 3c 02 00 0f 85 83 05 00 00 4d 8b bc 24 a0 03 00 00 48 b8 00 00 00 00 00 fc ff df 4c 89 fa 48 c1 ea 03 <0f> b6 14 02 4c 89 f8 83 e0 07 83 c0 01 38 d0 7c 08 84 d2 0f 85
RIP: fbcon_cursor+0x114/0x6f0 drivers/video/fbdev/core/fbcon.c:1325 RSP: ffff88809f4cfb48
---[ end trace 391cac51ffd925ae ]---

syzbot

unread,
Feb 12, 2020, 7:10:14 AM2/12/20
to syzkaller...@googlegroups.com
Hello,

syzbot found the following crash on:

HEAD commit: 35766839 Linux 4.19.103
git tree: linux-4.19.y
console output: https://syzkaller.appspot.com/x/log.txt?x=157cbfcde00000
kernel config: https://syzkaller.appspot.com/x/.config?x=84f14e7b6cbc7d27
dashboard link: https://syzkaller.appspot.com/bug?extid=44d06f09e5acfbfebdc8
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10e1887ee00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=101b4f01e00000

IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+44d06f...@syzkaller.appspotmail.com

audit: type=1400 audit(1581509213.161:36): avc: denied { map } for pid=8295 comm="syz-executor177" path="/root/syz-executor177002793" dev="sda1" ino=16484 scontext=unconfined_u:system_r:insmod_t:s0-s0:c0.c1023 tcontext=unconfined_u:object_r:user_home_t:s0 tclass=file permissive=1
kasan: CONFIG_KASAN_INLINE enabled
kasan: GPF could be caused by NULL-ptr deref or user memory access
general protection fault: 0000 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 14 Comm: kworker/0:1 Not tainted 4.19.103-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Workqueue: events console_callback
RIP: 0010:fbcon_cursor+0x114/0x7b0 drivers/video/fbdev/core/fbcon.c:1347
Code: 48 89 fa 48 c1 ea 03 80 3c 02 00 0f 85 43 06 00 00 4d 8b bc 24 a0 03 00 00 48 b8 00 00 00 00 00 fc ff df 4c 89 fa 48 c1 ea 03 <0f> b6 14 02 4c 89 f8 83 e0 07 83 c0 01 38 d0 7c 08 84 d2 0f 85 4d
RSP: 0018:ffff8880aa3afb00 EFLAGS: 00010203
RAX: dffffc0000000000 RBX: ffff8882196fdc80 RCX: ffffffff83b53100
RDX: 0000000020000001 RSI: ffffffff838908ec RDI: ffff8880827126a0
RBP: ffff8880aa3afb40 R08: ffff8880a54671e8 R09: ffffed1014b72f04
R10: ffffed1014b72f03 R11: ffff8880a5b9781f R12: ffff888082712300
R13: ffff8880a5466d80 R14: 0000000000000001 R15: 000000010000000c
FS: 0000000000000000(0000) GS:ffff8880ae800000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000f05d00 CR3: 00000000a9014000 CR4: 00000000001406f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
set_cursor drivers/tty/vt/vt.c:908 [inline]
set_cursor+0x1fb/0x280 drivers/tty/vt/vt.c:899
redraw_screen+0x60f/0x8e0 drivers/tty/vt/vt.c:1015
complete_change_console+0x105/0x3a0 drivers/tty/vt/vt_ioctl.c:1277
change_console+0x19b/0x2c0 drivers/tty/vt/vt_ioctl.c:1402
console_callback+0x3a1/0x400 drivers/tty/vt/vt.c:2800
process_one_work+0x989/0x1750 kernel/workqueue.c:2153
worker_thread+0x98/0xe40 kernel/workqueue.c:2296
kthread+0x354/0x420 kernel/kthread.c:246
ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:415
Modules linked in:
---[ end trace c46089ad2f94fde1 ]---
RIP: 0010:fbcon_cursor+0x114/0x7b0 drivers/video/fbdev/core/fbcon.c:1347
Code: 48 89 fa 48 c1 ea 03 80 3c 02 00 0f 85 43 06 00 00 4d 8b bc 24 a0 03 00 00 48 b8 00 00 00 00 00 fc ff df 4c 89 fa 48 c1 ea 03 <0f> b6 14 02 4c 89 f8 83 e0 07 83 c0 01 38 d0 7c 08 84 d2 0f 85 4d
RSP: 0018:ffff8880aa3afb00 EFLAGS: 00010203
RAX: dffffc0000000000 RBX: ffff8882196fdc80 RCX: ffffffff83b53100
RDX: 0000000020000001 RSI: ffffffff838908ec RDI: ffff8880827126a0
RBP: ffff8880aa3afb40 R08: ffff8880a54671e8 R09: ffffed1014b72f04
R10: ffffed1014b72f03 R11: ffff8880a5b9781f R12: ffff888082712300
R13: ffff8880a5466d80 R14: 0000000000000001 R15: 000000010000000c
FS: 0000000000000000(0000) GS:ffff8880ae800000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000f05d00 CR3: 00000000a9014000 CR4: 00000000001406f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400


---
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 syzk...@googlegroups.com.

syzbot will keep track of this bug report. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
syzbot can test patches for this bug, for details see:
https://goo.gl/tpsmEJ#testing-patches
Reply all
Reply to author
Forward
0 new messages