[Android 5.10] general protection fault in do_rmdir

0 views
Skip to first unread message

syzbot

unread,
Dec 8, 2023, 8:26:22 AM12/8/23
to syzkaller-a...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 0da9a7bcb7a2 Merge branch 'android13-5.10' into branch 'an..
git tree: android13-5.10-lts
console+strace: https://syzkaller.appspot.com/x/log.txt?x=136edbdce80000
kernel config: https://syzkaller.appspot.com/x/.config?x=45a04d39e92cbcf6
dashboard link: https://syzkaller.appspot.com/bug?extid=86ab3204ce3bfdb7de7a
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=126e08bae80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=15d6be28e80000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/67c14373e650/disk-0da9a7bc.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/404f1fbf1561/vmlinux-0da9a7bc.xz
kernel image: https://storage.googleapis.com/syzbot-assets/8affee670af0/bzImage-0da9a7bc.xz

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

general protection fault, probably for non-canonical address 0xdffffc0000000007: 0000 [#1] PREEMPT SMP KASAN
KASAN: null-ptr-deref in range [0x0000000000000038-0x000000000000003f]
CPU: 0 PID: 287 Comm: syz-executor210 Not tainted 5.10.200-syzkaller-00425-g0da9a7bcb7a2 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/09/2023
RIP: 0010:do_rmdir+0x28e/0x5c0 fs/namei.c:3911
Code: e8 87 c3 b6 ff 45 89 e5 48 bb 00 00 00 00 00 fc ff df eb 7c 49 8d 5c 24 30 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 14 34 f4 ff 48 83 3b 00 74 32 e8 49
RSP: 0018:ffffc90000b97de0 EFLAGS: 00010202
RAX: 0000000000000007 RBX: 0000000000000038 RCX: dffffc0000000000
RDX: 0000000000000000 RSI: 0000000000000003 RDI: 0000000000000000
RBP: ffffc90000b97f18 R08: ffffffff81b64f7b R09: ffffed1023810250
R10: 0000000000000000 R11: dffffc0000000001 R12: 0000000000000008
R13: ffff88811c081250 R14: 1ffff1102381024a R15: ffffc90000b97e01
FS: 00007f6e6bd696c0(0000) GS:ffff8881f7000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000020000400 CR3: 000000011ea44000 CR4: 00000000003506b0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
__do_sys_rmdir fs/namei.c:3936 [inline]
__se_sys_rmdir fs/namei.c:3934 [inline]
__x64_sys_rmdir+0x49/0x50 fs/namei.c:3934
do_syscall_64+0x34/0x70
entry_SYSCALL_64_after_hwframe+0x61/0xc6
RIP: 0033:0x7f6e6bda7479
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 c1 17 00 00 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 73 01 c3 48 c7 c1 b0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f6e6bd69218 EFLAGS: 00000246 ORIG_RAX: 0000000000000054
RAX: ffffffffffffffda RBX: 00007f6e6be34408 RCX: 00007f6e6bda7479
RDX: 00007f6e6bda7479 RSI: 00000000000f4240 RDI: 0000000020000080
RBP: 00007f6e6be34400 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007f6e6be0101c
R13: 00007f6e6be01038 R14: 00007f6e6bdff00e R15: 0030656c69662f30
Modules linked in:
---[ end trace c9bc1d7d8939e43b ]---
RIP: 0010:do_rmdir+0x28e/0x5c0 fs/namei.c:3911
Code: e8 87 c3 b6 ff 45 89 e5 48 bb 00 00 00 00 00 fc ff df eb 7c 49 8d 5c 24 30 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 14 34 f4 ff 48 83 3b 00 74 32 e8 49
RSP: 0018:ffffc90000b97de0 EFLAGS: 00010202
RAX: 0000000000000007 RBX: 0000000000000038 RCX: dffffc0000000000
RDX: 0000000000000000 RSI: 0000000000000003 RDI: 0000000000000000
RBP: ffffc90000b97f18 R08: ffffffff81b64f7b R09: ffffed1023810250
R10: 0000000000000000 R11: dffffc0000000001 R12: 0000000000000008
R13: ffff88811c081250 R14: 1ffff1102381024a R15: ffffc90000b97e01
FS: 00007f6e6bd696c0(0000) GS:ffff8881f7100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f6e6bd27d58 CR3: 000000011ea44000 CR4: 00000000003506a0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
----------------
Code disassembly (best guess):
0: e8 87 c3 b6 ff call 0xffb6c38c
5: 45 89 e5 mov %r12d,%r13d
8: 48 bb 00 00 00 00 00 movabs $0xdffffc0000000000,%rbx
f: fc ff df
12: eb 7c jmp 0x90
14: 49 8d 5c 24 30 lea 0x30(%r12),%rbx
19: 48 89 d8 mov %rbx,%rax
1c: 48 c1 e8 03 shr $0x3,%rax
20: 48 b9 00 00 00 00 00 movabs $0xdffffc0000000000,%rcx
27: fc ff df
* 2a: 80 3c 08 00 cmpb $0x0,(%rax,%rcx,1) <-- trapping instruction
2e: 74 08 je 0x38
30: 48 89 df mov %rbx,%rdi
33: e8 14 34 f4 ff call 0xfff4344c
38: 48 83 3b 00 cmpq $0x0,(%rbx)
3c: 74 32 je 0x70
3e: e8 .byte 0xe8
3f: 49 rex.WB


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

If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.

If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup

syzbot

unread,
Dec 8, 2023, 8:26:23 AM12/8/23
to syzkaller-a...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 0e7c7966689d ANDROID: GKI: db845c: Update symbols list and..
git tree: android13-5.15-lts
console+strace: https://syzkaller.appspot.com/x/log.txt?x=17ae72d2e80000
kernel config: https://syzkaller.appspot.com/x/.config?x=7c90e68490a9346d
dashboard link: https://syzkaller.appspot.com/bug?extid=119227d586c7650599dc
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14e3ab72e80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=153e5e30e80000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/bd636837f5d6/disk-0e7c7966.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/b8b2c56253e9/vmlinux-0e7c7966.xz
kernel image: https://storage.googleapis.com/syzbot-assets/b1265a06e5c0/bzImage-0e7c7966.xz

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

general protection fault, probably for non-canonical address 0xdffffc0000000007: 0000 [#1] PREEMPT SMP KASAN
KASAN: null-ptr-deref in range [0x0000000000000038-0x000000000000003f]
CPU: 0 PID: 293 Comm: syz-executor155 Not tainted 5.15.138-syzkaller-00281-g0e7c7966689d #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/10/2023
RIP: 0010:do_rmdir+0x339/0x630 fs/namei.c:4131
Code: ff 4c 89 64 24 50 72 0d e8 a4 79 b2 ff 45 89 fc e9 99 00 00 00 49 8d 5f 30 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 c9 7e f4 ff 48 83 3b 00 74 5d e8 6e
RSP: 0018:ffffc900007d7de0 EFLAGS: 00010202
RAX: 0000000000000007 RBX: 0000000000000038 RCX: dffffc0000000000
RDX: 0000000000000000 RSI: 0000000000000003 RDI: 0000000000000000
RBP: ffffc900007d7f08 R08: ffffffff81c01f70 R09: ffffed10237232b6
R10: 0000000000000000 R11: dffffc0000000001 R12: ffff88811b919580
R13: ffffc900007d7e60 R14: 1ffff110237232b0 R15: 0000000000000008
FS: 00007f379e10f6c0(0000) GS:ffff8881f7000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f379e0cdd58 CR3: 000000011e972000 CR4: 00000000003506b0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
__do_sys_rmdir fs/namei.c:4158 [inline]
__se_sys_rmdir fs/namei.c:4156 [inline]
__x64_sys_rmdir+0x49/0x50 fs/namei.c:4156
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x61/0xcb
RIP: 0033:0x7f379e14d549
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 c1 17 00 00 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 73 01 c3 48 c7 c1 b0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f379e10f218 EFLAGS: 00000246 ORIG_RAX: 0000000000000054
RAX: ffffffffffffffda RBX: 00007f379e1da408 RCX: 00007f379e14d549
RDX: 00007f379e14d549 RSI: 00000000000f4240 RDI: 0000000020000080
RBP: 00007f379e1da400 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007f379e1a701c
R13: 00007f379e1a7038 R14: 00007f379e1a500e R15: 0030656c69662f30
</TASK>
Modules linked in:
---[ end trace e2908ce7b846af04 ]---
RIP: 0010:do_rmdir+0x339/0x630 fs/namei.c:4131
Code: ff 4c 89 64 24 50 72 0d e8 a4 79 b2 ff 45 89 fc e9 99 00 00 00 49 8d 5f 30 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 c9 7e f4 ff 48 83 3b 00 74 5d e8 6e
RSP: 0018:ffffc900007d7de0 EFLAGS: 00010202
RAX: 0000000000000007 RBX: 0000000000000038 RCX: dffffc0000000000
RDX: 0000000000000000 RSI: 0000000000000003 RDI: 0000000000000000
RBP: ffffc900007d7f08 R08: ffffffff81c01f70 R09: ffffed10237232b6
R10: 0000000000000000 R11: dffffc0000000001 R12: ffff88811b919580
R13: ffffc900007d7e60 R14: 1ffff110237232b0 R15: 0000000000000008
FS: 00007f379e10f6c0(0000) GS:ffff8881f7000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f379e0cdd58 CR3: 000000011e972000 CR4: 00000000003506b0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
----------------
Code disassembly (best guess):
0: ff 4c 89 64 decl 0x64(%rcx,%rcx,4)
4: 24 50 and $0x50,%al
6: 72 0d jb 0x15
8: e8 a4 79 b2 ff call 0xffb279b1
d: 45 89 fc mov %r15d,%r12d
10: e9 99 00 00 00 jmp 0xae
15: 49 8d 5f 30 lea 0x30(%r15),%rbx
19: 48 89 d8 mov %rbx,%rax
1c: 48 c1 e8 03 shr $0x3,%rax
20: 48 b9 00 00 00 00 00 movabs $0xdffffc0000000000,%rcx
27: fc ff df
* 2a: 80 3c 08 00 cmpb $0x0,(%rax,%rcx,1) <-- trapping instruction
2e: 74 08 je 0x38
30: 48 89 df mov %rbx,%rdi
33: e8 c9 7e f4 ff call 0xfff47f01
38: 48 83 3b 00 cmpq $0x0,(%rbx)
3c: 74 5d je 0x9b
3e: e8 .byte 0xe8
3f: 6e outsb %ds:(%rsi),(%dx)

syzbot

unread,
Dec 8, 2023, 8:26:23 AM12/8/23
to syzkaller-a...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 6465e29536ed BACKPORT: HID: input: map battery system char..
git tree: android14-6.1
console+strace: https://syzkaller.appspot.com/x/log.txt?x=150ce7bae80000
kernel config: https://syzkaller.appspot.com/x/.config?x=2efa7ec05407068e
dashboard link: https://syzkaller.appspot.com/bug?extid=8f2a09a274a49e1a0dc3
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10f4af1ce80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=113651bae80000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/ca3be3a50640/disk-6465e295.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/475f637b0247/vmlinux-6465e295.xz
kernel image: https://storage.googleapis.com/syzbot-assets/d248f2486726/bzImage-6465e295.xz

The issue was bisected to:

commit 57f3ff9648991998d008ecf32f2f9e78a08bfb8b
Author: Daniel Rosenberg <dro...@google.com>
Date: Thu Dec 2 21:50:02 2021 +0000

ANDROID: fuse-bpf v1.1

bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=16a65ed2e80000
final oops: https://syzkaller.appspot.com/x/report.txt?x=15a65ed2e80000
console output: https://syzkaller.appspot.com/x/log.txt?x=11a65ed2e80000

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+8f2a09...@syzkaller.appspotmail.com
Fixes: 57f3ff964899 ("ANDROID: fuse-bpf v1.1")

Bug presence analysis results: the bug reproduces only on Android 6.1.


general protection fault, probably for non-canonical address 0xdffffc0000000007: 0000 [#1] PREEMPT SMP KASAN
KASAN: null-ptr-deref in range [0x0000000000000038-0x000000000000003f]
CPU: 1 PID: 300 Comm: syz-executor378 Not tainted 6.1.57-syzkaller-00085-g6465e29536ed #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/10/2023
RIP: 0010:do_rmdir+0x339/0x630 fs/namei.c:4174
Code: ff 4c 89 64 24 50 72 0d e8 d4 1b ad ff 45 89 fc e9 99 00 00 00 49 8d 5f 30 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 69 bb f3 ff 48 83 3b 00 74 5d e8 9e
RSP: 0018:ffffc90000d97de0 EFLAGS: 00010202
RAX: 0000000000000007 RBX: 0000000000000038 RCX: dffffc0000000000
RDX: 0000000000000000 RSI: 0000000000000003 RDI: 0000000000000000
RBP: ffffc90000d97f08 R08: ffffffff81caa66b R09: fffff520001b2f9b
R10: 0000000000000000 R11: dffffc0000000001 R12: ffff8881200fff10
R13: ffffc90000d97e60 R14: 1ffff1102401ffe2 R15: 0000000000000008
FS: 00007f413279a6c0(0000) GS:ffff8881f7100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00005555571bf350 CR3: 000000011f854000 CR4: 00000000003506a0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
__do_sys_rmdir fs/namei.c:4201 [inline]
__se_sys_rmdir fs/namei.c:4199 [inline]
__x64_sys_rmdir+0x49/0x50 fs/namei.c:4199
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f41327d8479
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 c1 17 00 00 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 73 01 c3 48 c7 c1 b0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f413279a218 EFLAGS: 00000246 ORIG_RAX: 0000000000000054
RAX: ffffffffffffffda RBX: 00007f4132865408 RCX: 00007f41327d8479
RDX: 00007f41327d8479 RSI: 00000000000f4240 RDI: 0000000020000080
RBP: 00007f4132865400 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007f413283201c
R13: 00007f4132832038 R14: 00007f413283000e R15: 0030656c69662f30
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:do_rmdir+0x339/0x630 fs/namei.c:4174
Code: ff 4c 89 64 24 50 72 0d e8 d4 1b ad ff 45 89 fc e9 99 00 00 00 49 8d 5f 30 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 69 bb f3 ff 48 83 3b 00 74 5d e8 9e
RSP: 0018:ffffc90000d97de0 EFLAGS: 00010202
RAX: 0000000000000007 RBX: 0000000000000038 RCX: dffffc0000000000
RDX: 0000000000000000 RSI: 0000000000000003 RDI: 0000000000000000
RBP: ffffc90000d97f08 R08: ffffffff81caa66b R09: fffff520001b2f9b
R10: 0000000000000000 R11: dffffc0000000001 R12: ffff8881200fff10
R13: ffffc90000d97e60 R14: 1ffff1102401ffe2 R15: 0000000000000008
FS: 00007f413279a6c0(0000) GS:ffff8881f7000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f4132758d58 CR3: 000000011f854000 CR4: 00000000003506b0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
----------------
Code disassembly (best guess):
0: ff 4c 89 64 decl 0x64(%rcx,%rcx,4)
4: 24 50 and $0x50,%al
6: 72 0d jb 0x15
8: e8 d4 1b ad ff call 0xffad1be1
d: 45 89 fc mov %r15d,%r12d
10: e9 99 00 00 00 jmp 0xae
15: 49 8d 5f 30 lea 0x30(%r15),%rbx
19: 48 89 d8 mov %rbx,%rax
1c: 48 c1 e8 03 shr $0x3,%rax
20: 48 b9 00 00 00 00 00 movabs $0xdffffc0000000000,%rcx
27: fc ff df
* 2a: 80 3c 08 00 cmpb $0x0,(%rax,%rcx,1) <-- trapping instruction
2e: 74 08 je 0x38
30: 48 89 df mov %rbx,%rdi
33: e8 69 bb f3 ff call 0xfff3bba1
38: 48 83 3b 00 cmpq $0x0,(%rbx)
3c: 74 5d je 0x9b
3e: e8 .byte 0xe8
3f: 9e sahf


---
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.
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
Reply all
Reply to author
Forward
0 new messages