Hello,
syzbot found the following crash on:
HEAD commit: d33692e8 Merge 4.14.74 into android-4.14
git tree: android-4.14
console output:
https://syzkaller.appspot.com/x/log.txt?x=167a2c91400000
kernel config:
https://syzkaller.appspot.com/x/.config?x=decf36ad71cd0a75
dashboard link:
https://syzkaller.appspot.com/bug?extid=5f472c8c84752c7e1c37
compiler: gcc (GCC) 8.0.1 20180413 (experimental)
syz repro:
https://syzkaller.appspot.com/x/repro.syz?x=13869ae6400000
C reproducer:
https://syzkaller.appspot.com/x/repro.c?x=1505126e400000
IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by:
syzbot+5f472c...@syzkaller.appspotmail.com
random: sshd: uninitialized urandom read (32 bytes read)
urandom_read: 1 callbacks suppressed
random: sshd: uninitialized urandom read (32 bytes read)
audit: type=1400 audit(1538731504.673:7): avc: denied { map } for
pid=1780 comm="syz-executor384" path="/root/syz-executor384052972"
dev="sda1" ino=16481 scontext=unconfined_u:system_r:insmod_t:s0-s0:c0.c1023
tcontext=unconfined_u:object_r:user_home_t:s0 tclass=file permissive=1
------------[ cut here ]------------
kernel BUG at security/keys/keyring.c:1221!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN NOPTI
Modules linked in:
CPU: 0 PID: 1780 Comm: syz-executor384 Not tainted 4.14.74+ #17
task: ffff8801cf415e00 task.stack: ffff8801cba88000
RIP: 0010:__key_link_begin+0x1f5/0x2b0 security/keys/keyring.c:1221
RSP: 0018:ffff8801cba8fc18 EFLAGS: 00010297
RAX: ffff8801cf415e00 RBX: ffff8801cc1c6000 RCX: 1ffff10039751f75
RDX: 0000000000000000 RSI: ffff8801cba8fd68 RDI: ffff8801cba8fd78
RBP: ffff8801cba8fd68 R08: 0000000000000001 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000001 R12: 1ffff10039751f91
R13: ffff8801cba8fd68 R14: ffff8801cc3e58a0 R15: ffff8801cba8fce8
FS: 0000000000c1f880(0000) GS:ffff8801d7600000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000020caaffb CR3: 00000001cf3dc002 CR4: 00000000001606b0
Call Trace:
construct_alloc_key security/keys/request_key.c:389 [inline]
construct_key_and_link security/keys/request_key.c:480 [inline]
request_key_and_link+0x50f/0xa20 security/keys/request_key.c:595
SYSC_request_key security/keys/keyctl.c:213 [inline]
SyS_request_key+0x20e/0x2c0 security/keys/keyctl.c:158
do_syscall_64+0x19b/0x4b0 arch/x86/entry/common.c:289
entry_SYSCALL_64_after_hwframe+0x42/0xb7
RIP: 0033:0x440169
RSP: 002b:00007ffdf9ce7e88 EFLAGS: 00000217 ORIG_RAX: 00000000000000f9
RAX: ffffffffffffffda RBX: 00000000004002c8 RCX: 0000000000440169
RDX: 00000000200001c0 RSI: 0000000020000180 RDI: 00000000200000c0
RBP: 00000000006ca018 R08: 00000000004002c8 R09: 00000000004002c8
R10: 00000000157535cf R11: 0000000000000217 R12: 00000000004019f0
R13: 0000000000401a80 R14: 0000000000000000 R15: 0000000000000000
Code: 94 ff 48 c7 c7 00 8e dd 8f e8 08 3f 83 ff eb ac e8 31 ef 94 ff 48 c7
c7 00 8e dd 8f e8 75 34 e9 00 e9 00 ff ff ff e8 1b ef 94 ff <0f> 0b e8 14
ef 94 ff 48 8d bb ce 00 00 00 48 b8 00 00 00 00 00
RIP: __key_link_begin+0x1f5/0x2b0 security/keys/keyring.c:1221 RSP:
ffff8801cba8fc18
---[ end trace aef62e2ed8133767 ]---
---
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