[Android 6.1] general protection fault in dev_map_enqueue

0 views
Skip to first unread message

syzbot

unread,
Mar 26, 2024, 7:53:19 PMMar 26
to syzkaller-a...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: eef3b6e52937 ANDROID: KVM: arm64: Fix TLB invalidation whe..
git tree: android14-6.1
console+strace: https://syzkaller.appspot.com/x/log.txt?x=10f10b91180000
kernel config: https://syzkaller.appspot.com/x/.config?x=54c503ca94c7e582
dashboard link: https://syzkaller.appspot.com/bug?extid=74f0fe424da0b5228a6f
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=13f4baa5180000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=10733769180000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/2821fbb60763/disk-eef3b6e5.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/bc0045a39cbd/vmlinux-eef3b6e5.xz
kernel image: https://storage.googleapis.com/syzbot-assets/1b4198d13d12/bzImage-eef3b6e5.xz

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

general protection fault, probably for non-canonical address 0xdffffc0000000000: 0000 [#1] PREEMPT SMP KASAN
KASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007]
CPU: 1 PID: 314 Comm: syz-executor264 Not tainted 6.1.68-syzkaller-00096-geef3b6e52937 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/29/2024
RIP: 0010:dev_map_enqueue+0x31/0x340 kernel/bpf/devmap.c:528
Code: 56 41 55 41 54 53 48 83 ec 18 48 89 55 c0 49 89 f7 48 89 fb 49 bc 00 00 00 00 00 fc ff df e8 f6 22 de ff 48 89 d8 48 c1 e8 03 <42> 80 3c 20 00 74 08 48 89 df e8 80 f6 24 00 4c 8b 33 48 83 c3 20
RSP: 0018:ffffc90000e77648 EFLAGS: 00010246
RAX: 0000000000000000 RBX: 0000000000000000 RCX: ffff8881098b8000
RDX: 0000000000000000 RSI: ffff8881223a3070 RDI: 0000000000000000
RBP: ffffc90000e77688 R08: 0000000000000005 R09: ffffffff8410be05
R10: 0000000000000004 R11: ffff8881098b8000 R12: dffffc0000000000
R13: 0000000000000000 R14: ffff8881f71364a0 R15: ffff8881223a3070
FS: 00005555570b4380(0000) GS:ffff8881f7100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fdadddcc0d0 CR3: 000000012224d000 CR4: 00000000003506a0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
__xdp_do_redirect_frame net/core/filter.c:4268 [inline]
xdp_do_redirect_frame+0x285/0x750 net/core/filter.c:4330
xdp_test_run_batch net/bpf/test_run.c:314 [inline]
bpf_test_run_xdp_live+0xc30/0x1f70 net/bpf/test_run.c:362
bpf_prog_test_run_xdp+0x7d1/0x1130 net/bpf/test_run.c:1387
bpf_prog_test_run+0x3b0/0x630 kernel/bpf/syscall.c:3635
__sys_bpf+0x59f/0x7f0 kernel/bpf/syscall.c:4990
__do_sys_bpf kernel/bpf/syscall.c:5076 [inline]
__se_sys_bpf kernel/bpf/syscall.c:5074 [inline]
__x64_sys_bpf+0x7c/0x90 kernel/bpf/syscall.c:5074
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7fdaddd54fb9
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 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffc612af718 EFLAGS: 00000246 ORIG_RAX: 0000000000000141
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007fdaddd54fb9
RDX: 0000000000000048 RSI: 0000000020000340 RDI: 000000000000000a
RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000006
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000000 R14: 0000000000000001 R15: 0000000000000001
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:dev_map_enqueue+0x31/0x340 kernel/bpf/devmap.c:528
Code: 56 41 55 41 54 53 48 83 ec 18 48 89 55 c0 49 89 f7 48 89 fb 49 bc 00 00 00 00 00 fc ff df e8 f6 22 de ff 48 89 d8 48 c1 e8 03 <42> 80 3c 20 00 74 08 48 89 df e8 80 f6 24 00 4c 8b 33 48 83 c3 20
RSP: 0018:ffffc90000e77648 EFLAGS: 00010246
RAX: 0000000000000000 RBX: 0000000000000000 RCX: ffff8881098b8000
RDX: 0000000000000000 RSI: ffff8881223a3070 RDI: 0000000000000000
RBP: ffffc90000e77688 R08: 0000000000000005 R09: ffffffff8410be05
R10: 0000000000000004 R11: ffff8881098b8000 R12: dffffc0000000000
R13: 0000000000000000 R14: ffff8881f71364a0 R15: ffff8881223a3070
FS: 00005555570b4380(0000) GS:ffff8881f7100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fdadddcc0d0 CR3: 000000012224d000 CR4: 00000000003506a0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
----------------
Code disassembly (best guess):
0: 56 push %rsi
1: 41 55 push %r13
3: 41 54 push %r12
5: 53 push %rbx
6: 48 83 ec 18 sub $0x18,%rsp
a: 48 89 55 c0 mov %rdx,-0x40(%rbp)
e: 49 89 f7 mov %rsi,%r15
11: 48 89 fb mov %rdi,%rbx
14: 49 bc 00 00 00 00 00 movabs $0xdffffc0000000000,%r12
1b: fc ff df
1e: e8 f6 22 de ff call 0xffde2319
23: 48 89 d8 mov %rbx,%rax
26: 48 c1 e8 03 shr $0x3,%rax
* 2a: 42 80 3c 20 00 cmpb $0x0,(%rax,%r12,1) <-- trapping instruction
2f: 74 08 je 0x39
31: 48 89 df mov %rbx,%rdi
34: e8 80 f6 24 00 call 0x24f6b9
39: 4c 8b 33 mov (%rbx),%r14
3c: 48 83 c3 20 add $0x20,%rbx


---
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
Reply all
Reply to author
Forward
0 new messages