Hello,
syzbot found the following issue on:
HEAD commit: 489e9c22 FROMGIT: kfence: show access type in report
git tree: android12-5.4
console output:
https://syzkaller.appspot.com/x/log.txt?x=10ad1098d00000
kernel config:
https://syzkaller.appspot.com/x/.config?x=5b365ba984b508e1
dashboard link:
https://syzkaller.appspot.com/bug?extid=eb653645362b461ad3ab
compiler: Debian clang version 11.0.1-2
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+eb6536...@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
CPU: 0 PID: 6847 Comm: syz-executor.1 Not tainted 5.4.97-syzkaller-00243-g489e9c226bb5 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:ioctl_permit_fill fs/incfs/pseudo_files.c:152 [inline]
RIP: 0010:pending_reads_dispatch_ioctl+0x5ec/0x2a60 fs/incfs/pseudo_files.c:906
Code: 45 89 ef 45 31 ed e9 ad 04 00 00 e8 1e 73 80 ff e9 0f 01 00 00 49 8d 5e 28 48 89 d8 48 c1 e8 03 48 b9 00 00 00 00 00 fc ff df <80> 3c 08 00 74 08 48 89 df e8 56 28 af ff 48 c7 c0 40 d9 fc 84 48
RSP: 0018:ffff8881dfb37940 EFLAGS: 00010206
RAX: 0000000000000005 RBX: 0000000000000028 RCX: dffffc0000000000
RDX: dffffc0000000000 RSI: ffff8881e9c03f00 RDI: ffff8881e9c042f4
RBP: ffff8881dfb37cb0 R08: ffffffff819eec57 R09: 0000000000000003
R10: ffffed103bf66f59 R11: 0000000000000004 R12: 1ffff1103bf66f58
R13: 1ffff1103c7ffe04 R14: 0000000000000000 R15: ffff8881e3fff020
FS: 00007fed56520700(0000) GS:ffff8881f6e00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007ffe33183cb8 CR3: 00000001ebc2d000 CR4: 00000000001406f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
do_vfs_ioctl+0x76a/0x1720 fs/ioctl.c:47
ksys_ioctl fs/ioctl.c:742 [inline]
__do_sys_ioctl fs/ioctl.c:749 [inline]
__se_sys_ioctl fs/ioctl.c:747 [inline]
__x64_sys_ioctl+0xd4/0x110 fs/ioctl.c:747
do_syscall_64+0xcb/0x150 arch/x86/entry/common.c:290
entry_SYSCALL_64_after_hwframe+0x44/0xa9
RIP: 0033:0x465b09
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 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 73 01 c3 48 c7 c1 bc ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fed56520188 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 000000000056bf60 RCX: 0000000000465b09
RDX: 0000000000400000 RSI: 0000000040046721 RDI: 0000000000000004
RBP: 00000000004b069f R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 000000000056bf60
R13: 00007fffc0d5302f R14: 00007fed56520300 R15: 0000000000022000
Modules linked in:
---[ end trace 759f57312370dc56 ]---
RIP: 0010:ioctl_permit_fill fs/incfs/pseudo_files.c:152 [inline]
RIP: 0010:pending_reads_dispatch_ioctl+0x5ec/0x2a60 fs/incfs/pseudo_files.c:906
Code: 45 89 ef 45 31 ed e9 ad 04 00 00 e8 1e 73 80 ff e9 0f 01 00 00 49 8d 5e 28 48 89 d8 48 c1 e8 03 48 b9 00 00 00 00 00 fc ff df <80> 3c 08 00 74 08 48 89 df e8 56 28 af ff 48 c7 c0 40 d9 fc 84 48
RSP: 0018:ffff8881dfb37940 EFLAGS: 00010206
RAX: 0000000000000005 RBX: 0000000000000028 RCX: dffffc0000000000
RDX: dffffc0000000000 RSI: ffff8881e9c03f00 RDI: ffff8881e9c042f4
RBP: ffff8881dfb37cb0 R08: ffffffff819eec57 R09: 0000000000000003
R10: ffffed103bf66f59 R11: 0000000000000004 R12: 1ffff1103bf66f58
R13: 1ffff1103c7ffe04 R14: 0000000000000000 R15: ffff8881e3fff020
FS: 00007fed56520700(0000) GS:ffff8881f6f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f1ab6418000 CR3: 00000001ebc2d000 CR4: 00000000001406e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
---
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.