BUG: unable to handle kernel paging request in do_con_trol

12 views
Skip to first unread message

syzbot

unread,
Dec 9, 2019, 9:41:11 AM12/9/19
to syzkaller...@googlegroups.com
Hello,

syzbot found the following crash on:

HEAD commit: fb683b5e Linux 4.19.88
git tree: linux-4.19.y
console output: https://syzkaller.appspot.com/x/log.txt?x=10a5781ee00000
kernel config: https://syzkaller.appspot.com/x/.config?x=aa0c39a6a0078b1c
dashboard link: https://syzkaller.appspot.com/bug?extid=69b47ab1682bdd85bee5
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+69b47a...@syzkaller.appspotmail.com

BUG: unable to handle kernel paging request at 000000010000000e
PGD 7b201067 P4D 7b201067 PUD 0
Oops: 0002 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 15677 Comm: syz-executor.4 Not tainted 4.19.88-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
RIP: 0010:memset16 arch/x86/include/asm/string_64.h:43 [inline]
RIP: 0010:scr_memsetw include/linux/vt_buffer.h:36 [inline]
RIP: 0010:csi_K drivers/tty/vt/vt.c:1559 [inline]
RIP: 0010:do_con_trol+0x39e6/0x6070 drivers/tty/vt/vt.c:2351
Code: 08 2c 01 0f 8e 81 13 00 00 4c 8b bd 08 ff ff ff 48 63 db 44 89 e9 41
0f b7 84 24 c8 03 00 00 48 01 db d1 e9 49 01 df 4c 89 ff <f3> 66 ab 49 8d
bc 24 78 04 00 00 b8 ff ff 37 00 48 89 fa 48 c1 e0
RSP: 0018:ffff88807c3b7780 EFLAGS: 00010202
RAX: 0000000000000720 RBX: 0000000000000000 RCX: 0000000000000001
RDX: 1ffff11009eca589 RSI: ffffffff83aedde9 RDI: 000000010000000e
RBP: ffff88807c3b78a0 R08: ffff888058ca6000 R09: 0000000000000005
R10: ffffed1015d04732 R11: ffff8880ae823993 R12: ffff88804f652880
R13: 0000000000000002 R14: 0000000000000001 R15: 000000010000000e
FS: 00007f52dc44a700(0000) GS:ffff8880ae800000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000010000000e CR3: 000000009f247000 CR4: 00000000001426f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
do_con_write.part.0+0xfd5/0x1eb0 drivers/tty/vt/vt.c:2773
do_con_write drivers/tty/vt/vt.c:2541 [inline]
con_write+0x46/0xd0 drivers/tty/vt/vt.c:3110
process_output_block drivers/tty/n_tty.c:593 [inline]
n_tty_write+0x3f9/0x10f0 drivers/tty/n_tty.c:2331
do_tty_write drivers/tty/tty_io.c:960 [inline]
tty_write+0x458/0x7a0 drivers/tty/tty_io.c:1044
__vfs_write+0x114/0x810 fs/read_write.c:485
vfs_write+0x20c/0x560 fs/read_write.c:549
ksys_write+0x14f/0x2d0 fs/read_write.c:599
__do_sys_write fs/read_write.c:611 [inline]
__se_sys_write fs/read_write.c:608 [inline]
__x64_sys_write+0x73/0xb0 fs/read_write.c:608
do_syscall_64+0xfd/0x620 arch/x86/entry/common.c:293
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x45a6f9
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:00007f52dc449c78 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 0000000000000003 RCX: 000000000045a6f9
RDX: 0000000000000078 RSI: 0000000020000200 RDI: 0000000000000003
RBP: 000000000075bf20 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007f52dc44a6d4
R13: 00000000004cbbaf R14: 00000000004e5858 R15: 00000000ffffffff
Modules linked in:
CR2: 000000010000000e
UBIFS error (pid: 15680): cannot open "udev/nbd0", error -22
---[ end trace f33faad8cb051993 ]---
RIP: 0010:memset16 arch/x86/include/asm/string_64.h:43 [inline]
RIP: 0010:scr_memsetw include/linux/vt_buffer.h:36 [inline]
RIP: 0010:csi_K drivers/tty/vt/vt.c:1559 [inline]
RIP: 0010:do_con_trol+0x39e6/0x6070 drivers/tty/vt/vt.c:2351
Code: 08 2c 01 0f 8e 81 13 00 00 4c 8b bd 08 ff ff ff 48 63 db 44 89 e9 41
0f b7 84 24 c8 03 00 00 48 01 db d1 e9 49 01 df 4c 89 ff <f3> 66 ab 49 8d
bc 24 78 04 00 00 b8 ff ff 37 00 48 89 fa 48 c1 e0
RSP: 0018:ffff88807c3b7780 EFLAGS: 00010202
RAX: 0000000000000720 RBX: 0000000000000000 RCX: 0000000000000001
RDX: 1ffff11009eca589 RSI: ffffffff83aedde9 RDI: 000000010000000e
RBP: ffff88807c3b78a0 R08: ffff888058ca6000 R09: 0000000000000005
R10: ffffed1015d04732 R11: ffff8880ae823993 R12: ffff88804f652880
R13: 0000000000000002 R14: 0000000000000001 R15: 000000010000000e
FS: 00007f52dc44a700(0000) GS:ffff8880ae800000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000001fff038 CR3: 000000009f247000 CR4: 00000000001426f0
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

unread,
Dec 9, 2019, 11:57:09 AM12/9/19
to syzkaller...@googlegroups.com
syzbot has found a reproducer for the following crash on:

HEAD commit: fb683b5e Linux 4.19.88
git tree: linux-4.19.y
console output: https://syzkaller.appspot.com/x/log.txt?x=149ff061e00000
kernel config: https://syzkaller.appspot.com/x/.config?x=aa0c39a6a0078b1c
dashboard link: https://syzkaller.appspot.com/bug?extid=69b47ab1682bdd85bee5
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11b9e77ae00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=131c0232e00000

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

audit: type=1400 audit(1575910401.234:36): avc: denied { map } for
pid=7753 comm="syz-executor585" path="/root/syz-executor585688742"
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
BUG: unable to handle kernel paging request at 000000010000000e
PGD 8097b067 P4D 8097b067 PUD 0
Oops: 0002 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 7753 Comm: syz-executor585 Not tainted 4.19.88-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
RIP: 0010:memset16 arch/x86/include/asm/string_64.h:43 [inline]
RIP: 0010:scr_memsetw include/linux/vt_buffer.h:36 [inline]
RIP: 0010:csi_K drivers/tty/vt/vt.c:1559 [inline]
RIP: 0010:do_con_trol+0x39e6/0x6070 drivers/tty/vt/vt.c:2351
Code: 08 2c 01 0f 8e 81 13 00 00 4c 8b bd 08 ff ff ff 48 63 db 44 89 e9 41
0f b7 84 24 c8 03 00 00 48 01 db d1 e9 49 01 df 4c 89 ff <f3> 66 ab 49 8d
bc 24 78 04 00 00 b8 ff ff 37 00 48 89 fa 48 c1 e0
RSP: 0018:ffff88809b8c7780 EFLAGS: 00010202
RAX: 0000000000000720 RBX: 0000000000000000 RCX: 0000000000000001
RDX: 1ffff1101400c879 RSI: ffffffff83aedde9 RDI: 000000010000000e
RBP: ffff88809b8c78a0 R08: ffff88807f8fe500 R09: 0000000000000005
R10: ffffed1015d04732 R11: ffff8880ae823993 R12: ffff8880a0064000
R13: 0000000000000002 R14: 0000000000000001 R15: 000000010000000e
FS: 00000000008b1880(0000) GS:ffff8880ae800000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000010000000e CR3: 00000000a4cf1000 CR4: 00000000001406f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
do_con_write.part.0+0xfd5/0x1eb0 drivers/tty/vt/vt.c:2773
do_con_write drivers/tty/vt/vt.c:2541 [inline]
con_write+0x46/0xd0 drivers/tty/vt/vt.c:3110
process_output_block drivers/tty/n_tty.c:593 [inline]
n_tty_write+0x3f9/0x10f0 drivers/tty/n_tty.c:2331
do_tty_write drivers/tty/tty_io.c:960 [inline]
tty_write+0x458/0x7a0 drivers/tty/tty_io.c:1044
__vfs_write+0x114/0x810 fs/read_write.c:485
vfs_write+0x20c/0x560 fs/read_write.c:549
ksys_write+0x14f/0x2d0 fs/read_write.c:599
__do_sys_write fs/read_write.c:611 [inline]
__se_sys_write fs/read_write.c:608 [inline]
__x64_sys_write+0x73/0xb0 fs/read_write.c:608
do_syscall_64+0xfd/0x620 arch/x86/entry/common.c:293
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x4404f9
Code: 18 89 d0 c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 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 5b 14 fc ff c3 66 2e 0f 1f 84 00 00 00 00
RSP: 002b:00007fffa2be5538 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 00000000004002c8 RCX: 00000000004404f9
RDX: 0000000000000078 RSI: 0000000020000200 RDI: 0000000000000004
RBP: 00000000006ca018 R08: 0000000000000000 R09: 00000000004002c8
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000401de0
R13: 0000000000401e70 R14: 0000000000000000 R15: 0000000000000000
Modules linked in:
CR2: 000000010000000e
---[ end trace aa1d2f8c28a58c33 ]---
RIP: 0010:memset16 arch/x86/include/asm/string_64.h:43 [inline]
RIP: 0010:scr_memsetw include/linux/vt_buffer.h:36 [inline]
RIP: 0010:csi_K drivers/tty/vt/vt.c:1559 [inline]
RIP: 0010:do_con_trol+0x39e6/0x6070 drivers/tty/vt/vt.c:2351
Code: 08 2c 01 0f 8e 81 13 00 00 4c 8b bd 08 ff ff ff 48 63 db 44 89 e9 41
0f b7 84 24 c8 03 00 00 48 01 db d1 e9 49 01 df 4c 89 ff <f3> 66 ab 49 8d
bc 24 78 04 00 00 b8 ff ff 37 00 48 89 fa 48 c1 e0
RSP: 0018:ffff88809b8c7780 EFLAGS: 00010202
RAX: 0000000000000720 RBX: 0000000000000000 RCX: 0000000000000001
RDX: 1ffff1101400c879 RSI: ffffffff83aedde9 RDI: 000000010000000e
RBP: ffff88809b8c78a0 R08: ffff88807f8fe500 R09: 0000000000000005
R10: ffffed1015d04732 R11: ffff8880ae823993 R12: ffff8880a0064000
R13: 0000000000000002 R14: 0000000000000001 R15: 000000010000000e
FS: 00000000008b1880(0000) GS:ffff8880ae800000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000010000000e CR3: 00000000a4cf1000 CR4: 00000000001406f0

syzbot

unread,
Dec 9, 2019, 12:13:11 PM12/9/19
to syzkaller...@googlegroups.com
Hello,

syzbot found the following crash on:

HEAD commit: a844dc4c Linux 4.14.158
git tree: linux-4.14.y
console output: https://syzkaller.appspot.com/x/log.txt?x=11129c2ae00000
kernel config: https://syzkaller.appspot.com/x/.config?x=c02bef505ffc02ff
dashboard link: https://syzkaller.appspot.com/bug?extid=b278b6a526f6a5af5fc6
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=16c82b7ae00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=174b7c82e00000

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

audit: type=1400 audit(1575911417.577:36): avc: denied { map } for
pid=6980 comm="syz-executor237" path="/root/syz-executor237277072"
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
BUG: unable to handle kernel paging request at 000000010000000e
IP: memset16 arch/x86/include/asm/string_64.h:58 [inline]
IP: scr_memsetw include/linux/vt_buffer.h:36 [inline]
IP: csi_K drivers/tty/vt/vt.c:1222 [inline]
IP: do_con_trol+0x2fac/0x5b40 drivers/tty/vt/vt.c:2013
PGD 8ea9a067 P4D 8ea9a067 PUD 0
Oops: 0002 [#1] PREEMPT SMP KASAN
Modules linked in:
CPU: 1 PID: 6980 Comm: syz-executor237 Not tainted 4.14.158-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
task: ffff8880a950c300 task.stack: ffff888098ec0000
RIP: 0010:memset16 arch/x86/include/asm/string_64.h:58 [inline]
RIP: 0010:scr_memsetw include/linux/vt_buffer.h:36 [inline]
RIP: 0010:csi_K drivers/tty/vt/vt.c:1222 [inline]
RIP: 0010:do_con_trol+0x2fac/0x5b40 drivers/tty/vt/vt.c:2013
RSP: 0018:ffff888098ec7878 EFLAGS: 00010202
RAX: 0000000000000720 RBX: 1ffff110131d8f13 RCX: 0000000000000001
RDX: 1ffff110100fbe51 RSI: 1ffff110100fbe67 RDI: 000000010000000e
RBP: ffff888098ec7960 R08: ffff8880807df28c R09: 0000000000000002
R10: 0000000000000000 R11: ffff8880a950c300 R12: ffff8880807deec0
R13: 0000000000000001 R14: 000000010000000e R15: 0000000000000002
FS: 0000000000e53880(0000) GS:ffff8880aed00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000010000000e CR3: 00000000a4870000 CR4: 00000000001406e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
do_con_write.part.0+0xcc7/0x1b50 drivers/tty/vt/vt.c:2434
do_con_write drivers/tty/vt/vt.c:2205 [inline]
con_write+0x38/0xc0 drivers/tty/vt/vt.c:2787
process_output_block drivers/tty/n_tty.c:595 [inline]
n_tty_write+0x38b/0xee0 drivers/tty/n_tty.c:2333
do_tty_write drivers/tty/tty_io.c:959 [inline]
tty_write+0x3f6/0x700 drivers/tty/tty_io.c:1043
__vfs_write+0x105/0x6b0 fs/read_write.c:480
vfs_write+0x198/0x500 fs/read_write.c:544
SYSC_write fs/read_write.c:590 [inline]
SyS_write+0xfd/0x230 fs/read_write.c:582
do_syscall_64+0x1e8/0x640 arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x42/0xb7
RIP: 0033:0x4404f9
RSP: 002b:00007ffed2974698 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 00000000004002c8 RCX: 00000000004404f9
RDX: 0000000000000078 RSI: 0000000020000200 RDI: 0000000000000004
RBP: 00000000006ca018 R08: 0000000000000000 R09: 00000000004002c8
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000401de0
R13: 0000000000401e70 R14: 0000000000000000 R15: 0000000000000000
Code: c1 e0 2a 48 89 fa 48 c1 ea 03 0f b6 04 02 84 c0 74 08 2c 01 0f 8e e4
29 00 00 41 0f b7 84 24 c8 03 00 00 44 89 f9 4c 89 f7 d1 e9 <f3> 66 ab 49
8d bc 24 78 04 00 00 b8 ff ff 37 00 48 89 fa 48 c1
RIP: memset16 arch/x86/include/asm/string_64.h:58 [inline] RSP:
ffff888098ec7878
RIP: scr_memsetw include/linux/vt_buffer.h:36 [inline] RSP: ffff888098ec7878
RIP: csi_K drivers/tty/vt/vt.c:1222 [inline] RSP: ffff888098ec7878
RIP: do_con_trol+0x2fac/0x5b40 drivers/tty/vt/vt.c:2013 RSP:
ffff888098ec7878
CR2: 000000010000000e
---[ end trace 9ed48a5e027adfcd ]---


---
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

syzbot

unread,
Aug 27, 2020, 8:26:05 PM8/27/20
to syzkaller...@googlegroups.com
syzbot suspects this issue was fixed by commit:

commit 74752b81eae8ae64e97de222320026367e92c4b5
Author: Tetsuo Handa <penguin...@I-love.SAKURA.ne.jp>
Date: Sun Jul 12 11:10:12 2020 +0000

vt: Reject zero-sized screen buffer size.

bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=13244fb1900000
start commit: dc4ba5be Linux 4.19.97
git tree: linux-4.19.y
kernel config: https://syzkaller.appspot.com/x/.config?x=cc17a984a7e9c2f3
dashboard link: https://syzkaller.appspot.com/bug?extid=69b47ab1682bdd85bee5
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=175d32d6e00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16842079e00000

If the result looks correct, please mark the issue as fixed by replying with:

#syz fix: vt: Reject zero-sized screen buffer size.

For information about bisection process see: https://goo.gl/tpsmEJ#bisection
Reply all
Reply to author
Forward
0 new messages