syzbot


BUG: unable to handle kernel paging request in crypto_chacha20_crypt

Status: closed as dup on 2017/12/03 19:11
Reported-by: syzbot+a2aae0656fcdc9990e110e63998f859a38854fde@syzkaller.appspotmail.com
First crash: 1671d, last: 1651d
Duplicate of (1):
Title Repro Cause bisect Fix bisect Count Last Reported
general protection fault in crypto_chacha20_crypt C 2374 1640d 1672d

Sample crash report:
BUG: unable to handle kernel paging request at 00000000b16e64b2
IP: crypto_chacha20_init crypto/chacha20_generic.c:58 [inline]
IP: crypto_chacha20_crypt+0x557/0xbd0 crypto/chacha20_generic.c:91
PGD 5e28067 P4D 5e28067 PUD 0 
Oops: 0000 [#1] SMP KASAN
Dumping ftrace buffer:
   (ftrace buffer empty)
Modules linked in:
CPU: 1 PID: 3080 Comm: syzkaller155751 Not tainted 4.15.0-rc2+ #206
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
task: 00000000f2a928ab task.stack: 000000006f8e42ad
RIP: 0010:crypto_chacha20_init crypto/chacha20_generic.c:58 [inline]
RIP: 0010:crypto_chacha20_crypt+0x557/0xbd0 crypto/chacha20_generic.c:91
RSP: 0018:ffff8801cb83f680 EFLAGS: 00010246
RAX: ffff8801cb83f6f0 RBX: 00000000e6000000 RCX: ffffffff822679cb
RDX: 0000000000000000 RSI: ffff8801ce919e00 RDI: ffff8801cb83f71c
RBP: ffff8801cb83f8a0 R08: ffffed0039821d8c R09: ffff8801cc10ec40
R10: ffff8801cb83f8b8 R11: ffffed0039821d8b R12: 0000000000000000
R13: ffffffff00000001 R14: 0000000000000000 R15: dffffc0000000000
FS:  0000000001102880(0000) GS:ffff8801db500000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffffff00000001 CR3: 00000001db1c3000 CR4: 00000000001406e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 crypto_skcipher_decrypt include/crypto/skcipher.h:463 [inline]
 _skcipher_recvmsg crypto/algif_skcipher.c:126 [inline]
 skcipher_recvmsg+0x739/0xf20 crypto/algif_skcipher.c:165
 sock_recvmsg_nosec net/socket.c:805 [inline]
 sock_recvmsg+0xc9/0x110 net/socket.c:812
 sock_read_iter+0x361/0x560 net/socket.c:889
 call_read_iter include/linux/fs.h:1766 [inline]
 aio_read+0x2b0/0x3a0 fs/aio.c:1501
 io_submit_one fs/aio.c:1611 [inline]
 do_io_submit+0xf99/0x14f0 fs/aio.c:1682
 SYSC_io_submit fs/aio.c:1707 [inline]
 SyS_io_submit+0x27/0x30 fs/aio.c:1704
 entry_SYSCALL_64_fastpath+0x1f/0x96
RIP: 0033:0x43ffb9
RSP: 002b:00007ffec2af4598 EFLAGS: 00000203 ORIG_RAX: 00000000000000d1
RAX: ffffffffffffffda RBX: 00000000004002c8 RCX: 000000000043ffb9
RDX: 0000000020738000 RSI: 0000000000000002 RDI: 00007efd21d84000
RBP: 00000000006ca018 R08: 0000000000401920 R09: 0000000000401920
R10: 0000000000000000 R11: 0000000000000203 R12: 0000000000401920
R13: 00000000004019b0 R14: 0000000000000000 R15: 0000000000000000
Code: df 89 9d 7c fe ff ff 48 c1 ea 03 0f b6 14 02 4c 89 e8 83 e0 07 83 c0 03 38 d0 7c 08 84 d2 0f 85 99 05 00 00 48 8b 85 28 fe ff ff <41> 8b 5d 00 48 8d 78 30 48 b8 00 00 00 00 00 fc ff df 48 89 fa 
RIP: crypto_chacha20_init crypto/chacha20_generic.c:58 [inline] RSP: ffff8801cb83f680
RIP: crypto_chacha20_crypt+0x557/0xbd0 crypto/chacha20_generic.c:91 RSP: ffff8801cb83f680
CR2: ffffffff00000001
---[ end trace 5bd338678f0ad697 ]---

Crashes (24):
Manager Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Title
ci-upstream-kasan-gce 2017/12/04 03:55 upstream ae64f9bd1d36 48359b97 .config log report syz C
ci-upstream-next-kasan-gce 2017/12/04 23:52 linux-next 7cc61a0a562c 48359b97 .config log report syz C
ci-upstream-mmots-kasan-gce 2017/12/03 23:39 mmots 4131d5166185 29b0fd90 .config log report syz C
ci-upstream-kasan-gce 2017/12/19 04:06 upstream ace52288edf0 1c4160ef .config log report
ci-upstream-kasan-gce 2017/12/19 04:06 upstream ace52288edf0 1c4160ef .config log report
ci-upstream-kasan-gce 2017/12/11 05:38 upstream 51090c5d6de0 5ad0ce95 .config log report
ci-upstream-kasan-gce 2017/12/10 02:31 upstream 4ded3bec65a0 5ad0ce95 .config log report
ci-upstream-kasan-gce 2017/12/06 18:56 upstream 328b4ed93b69 5d643f8e .config log report
ci-upstream-kasan-gce 2017/12/05 11:07 upstream fd6d2e506ce6 de212f1a .config log report
ci-upstream-net-kasan-gce 2017/12/17 08:34 net-next c30abd5e40dd b6f0c91b .config log report
ci-upstream-net-kasan-gce 2017/12/15 21:34 net-next 3b07d7884ca2 ac20b98c .config log report
ci-upstream-net-kasan-gce 2017/12/14 00:50 net-next f93ea3bf151d 06ea774d .config log report
ci-upstream-net-kasan-gce 2017/12/13 01:11 net-next c360f2b58ee4 414a185f .config log report
ci-upstream-net-kasan-gce 2017/12/12 09:17 net-next c360f2b58ee4 da131727 .config log report
ci-upstream-net-kasan-gce 2017/12/11 15:25 net-next a0b586fa75a6 27f5dfef .config log report
ci-upstream-net-kasan-gce 2017/12/07 20:59 net-next 24e5992a6bae 5d643f8e .config log report
ci-upstream-mmots-kasan-gce 2017/12/19 04:07 mmots 82bcf1def3b5 1c4160ef .config log report
ci-upstream-mmots-kasan-gce 2017/12/15 05:46 mmots 82bcf1def3b5 ac20b98c .config log report
ci-upstream-next-kasan-gce 2017/12/10 07:37 linux-next ad4dac17f9d5 5ad0ce95 .config log report
ci-upstream-mmots-kasan-gce 2017/12/09 06:54 mmots 82bcf1def3b5 5ad0ce95 .config log report
ci-upstream-next-kasan-gce 2017/12/06 20:02 linux-next d5c52866f560 5d643f8e .config log report
ci-upstream-mmots-kasan-gce 2017/12/04 05:58 mmots 4131d5166185 29b0fd90 .config log report
ci-upstream-mmots-kasan-gce 2017/11/28 20:46 mmots dbf9f9124937 1808de66 .config log report
ci-upstream-next-kasan-gce 2017/11/28 20:13 linux-next 5bef2980adef 1808de66 .config log report