general protection fault in aa_sk_perm

9 views
Skip to first unread message

syzbot

unread,
Nov 8, 2021, 5:54:18 AM11/8/21
to syzkaller-upst...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: ce840177930f Merge tag 'defconfig-5.16' of git://git.kerne..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=10ffa712b00000
kernel config: https://syzkaller.appspot.com/x/.config?x=647adc5a101c9bf3
dashboard link: https://syzkaller.appspot.com/bug?extid=0bf3916919bff3ae3ebf
compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
CC: [and...@kernel.org a...@kernel.org b...@vger.kernel.org dan...@iogearbox.net jmo...@namei.org john.fa...@gmail.com ka...@fb.com kps...@kernel.org linux-...@vger.kernel.org linux-secu...@vger.kernel.org net...@vger.kernel.org se...@hallyn.com songliu...@fb.com y...@fb.com]

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+0bf391...@syzkaller.appspotmail.com

general protection fault, probably for non-canonical address 0xdffffc0000000001: 0000 [#1] PREEMPT SMP KASAN
KASAN: null-ptr-deref in range [0x0000000000000008-0x000000000000000f]
CPU: 0 PID: 32123 Comm: systemd-udevd Not tainted 5.15.0-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:aa_sk_perm+0x155/0xaa0 security/apparmor/include/cred.h:27
Code: e8 07 00 00 48 63 05 5a e3 8b 07 48 01 c5 0f 84 d4 05 00 00 e8 4c d9 ce fd 48 89 ea 48 b8 00 00 00 00 00 fc ff df 48 c1 ea 03 <80> 3c 02 00 0f 85 c9 08 00 00 48 8b 6d 00 48 85 ed 0f 84 e5 05 00
RSP: 0018:ffffc9000aa9fa08 EFLAGS: 00010212
RAX: dffffc0000000000 RBX: ffffffff8b34ce10 RCX: 0000000000000000
RDX: 0000000000000001 RSI: ffffffff83a8eac4 RDI: ffff888000103388
RBP: 0000000000000008 R08: 0000000000000000 R09: 0000000000000000
R10: ffffffff83a8ea16 R11: 0000000000000000 R12: ffff888080e9da00
R13: 1ffff92001553f47 R14: ffff888082313000 R15: ffff888080e9da00
FS: 00007f9c7225a8c0(0000) GS:ffff8880b9c00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007ffd2fa4bc47 CR3: 000000007acf8000 CR4: 0000000000350ef0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000600
Call Trace:
<TASK>
security_socket_recvmsg+0x5c/0xc0 security/security.c:2213
sock_recvmsg net/socket.c:960 [inline]
____sys_recvmsg+0x238/0x600 net/socket.c:2628
___sys_recvmsg+0x127/0x200 net/socket.c:2670
__sys_recvmsg+0xe2/0x1a0 net/socket.c:2700
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x44/0xae
RIP: 0033:0x7f9c713a0dc7
Code: 89 01 b8 ff ff ff ff eb d8 66 2e 0f 1f 84 00 00 00 00 00 8b 05 0a b6 20 00 85 c0 75 2e 48 63 ff 48 63 d2 b8 2f 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 01 c3 48 8b 15 b1 71 20 00 f7 d8 64 89 02 48
RSP: 002b:00007ffd2fa4bc18 EFLAGS: 00000246 ORIG_RAX: 000000000000002f
RAX: ffffffffffffffda RBX: 00007ffd2fa4dea0 RCX: 00007f9c713a0dc7
RDX: 0000000000000000 RSI: 00007ffd2fa4bcb0 RDI: 000000000000000e
RBP: 00007ffd2fa4df50 R08: 0000000000000049 R09: 0000000000000018
R10: 00000000ffffffff R11: 0000000000000246 R12: 000055e4945b34e0
R13: 00007ffd2fa4deac R14: 00007ffd2fa4bd90 R15: 000000000000000e
</TASK>
Modules linked in:
---[ end trace ae0c8003b1409144 ]---
RIP: 0010:aa_sk_perm+0x155/0xaa0 security/apparmor/include/cred.h:27
Code: e8 07 00 00 48 63 05 5a e3 8b 07 48 01 c5 0f 84 d4 05 00 00 e8 4c d9 ce fd 48 89 ea 48 b8 00 00 00 00 00 fc ff df 48 c1 ea 03 <80> 3c 02 00 0f 85 c9 08 00 00 48 8b 6d 00 48 85 ed 0f 84 e5 05 00
RSP: 0018:ffffc9000aa9fa08 EFLAGS: 00010212
RAX: dffffc0000000000 RBX: ffffffff8b34ce10 RCX: 0000000000000000
RDX: 0000000000000001 RSI: ffffffff83a8eac4 RDI: ffff888000103388
RBP: 0000000000000008 R08: 0000000000000000 R09: 0000000000000000
R10: ffffffff83a8ea16 R11: 0000000000000000 R12: ffff888080e9da00
R13: 1ffff92001553f47 R14: ffff888082313000 R15: ffff888080e9da00
FS: 00007f9c7225a8c0(0000) GS:ffff8880b9c00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007ffd2fa4bc47 CR3: 000000007acf8000 CR4: 0000000000350ef0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000600
----------------
Code disassembly (best guess):
0: e8 07 00 00 48 callq 0x4800000c
5: 63 05 5a e3 8b 07 movsxd 0x78be35a(%rip),%eax # 0x78be365
b: 48 01 c5 add %rax,%rbp
e: 0f 84 d4 05 00 00 je 0x5e8
14: e8 4c d9 ce fd callq 0xfdced965
19: 48 89 ea mov %rbp,%rdx
1c: 48 b8 00 00 00 00 00 movabs $0xdffffc0000000000,%rax
23: fc ff df
26: 48 c1 ea 03 shr $0x3,%rdx
* 2a: 80 3c 02 00 cmpb $0x0,(%rdx,%rax,1) <-- trapping instruction
2e: 0f 85 c9 08 00 00 jne 0x8fd
34: 48 8b 6d 00 mov 0x0(%rbp),%rbp
38: 48 85 ed test %rbp,%rbp
3b: 0f .byte 0xf
3c: 84 e5 test %ah,%ch
3e: 05 .byte 0x5


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

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

syzbot

unread,
Feb 2, 2022, 5:47:19 AM2/2/22
to syzkaller-upst...@googlegroups.com
Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.
Reply all
Reply to author
Forward
0 new messages