| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <000000000000f6531b061494e696@google.com> Date: Tue, 26 Mar 2024 12:00:22 -0700 From: syzbot <syzbot+af9492708df9797198d6@...kaller.appspotmail.com> To: andrii@...nel.org, ast@...nel.org, bpf@...r.kernel.org, daniel@...earbox.net, davem@...emloft.net, eddyz87@...il.com, haoluo@...gle.com, hawk@...nel.org, john.fastabend@...il.com, jolsa@...nel.org, kpsingh@...nel.org, kuba@...nel.org, linux-kernel@...r.kernel.org, martin.lau@...ux.dev, netdev@...r.kernel.org, sdf@...gle.com, song@...nel.org, syzkaller-bugs@...glegroups.com, yonghong.song@...ux.dev Subject: [syzbot] [bpf?] [net?] general protection fault in dev_map_enqueue Hello, syzbot found the following issue on: HEAD commit: fe46a7dd189e Merge tag 'sound-6.9-rc1' of git://git.kernel.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=158ad421180000 kernel config: https://syzkaller.appspot.com/x/.config?x=fe78468a74fdc3b7 dashboard link: https://syzkaller.appspot.com/bug?extid=af9492708df9797198d6 compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40 Unfortunately, I don't have any reproducer for this issue yet. Downloadable assets: disk image: https://storage.googleapis.com/syzbot-assets/0f7abe4afac7/disk-fe46a7dd.raw.xz vmlinux: https://storage.googleapis.com/syzbot-assets/82598d09246c/vmlinux-fe46a7dd.xz kernel image: https://storage.googleapis.com/syzbot-assets/efa23788c875/bzImage-fe46a7dd.xz IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+af9492708df9797198d6@...kaller.appspotmail.com general protection fault, probably for non-canonical address 0xdffffc0000000000: 0000 [#1] PREEMPT SMP KASAN NOPTI KASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007] CPU: 1 PID: 13398 Comm: syz-executor.3 Not tainted 6.8.0-syzkaller-08951-gfe46a7dd189e #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/29/2024 RIP: 0010:dev_map_enqueue+0x31/0x3e0 kernel/bpf/devmap.c:539 Code: 41 56 41 55 41 54 53 48 83 ec 18 49 89 d4 49 89 f5 48 89 fd 49 be 00 00 00 00 00 fc ff df e8 56 3a d8 ff 48 89 e8 48 c1 e8 03 <42> 80 3c 30 00 74 08 48 89 ef e8 60 89 3b 00 4c 8b 7d 00 48 83 c5 RSP: 0018:ffffc90010e6f688 EFLAGS: 00010256 RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000040000 RDX: ffffc9000fb19000 RSI: 0000000000000c96 RDI: 0000000000000c97 RBP: 0000000000000000 R08: 0000000000000005 R09: ffffffff8954502e R10: 0000000000000004 R11: ffff88805bde3c00 R12: ffff88807e182000 R13: ffff88805595d070 R14: dffffc0000000000 R15: ffff8880b953c288 FS: 00007fe7632126c0(0000) GS:ffff8880b9500000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000001b32d23000 CR3: 000000006b1cc000 CR4: 0000000000350ef0 Call Trace: <TASK> __xdp_do_redirect_frame net/core/filter.c:4384 [inline] xdp_do_redirect_frame+0x20d/0x4d0 net/core/filter.c:4438 xdp_test_run_batch net/bpf/test_run.c:336 [inline] bpf_test_run_xdp_live+0xe8a/0x1e90 net/bpf/test_run.c:384 bpf_prog_test_run_xdp+0x813/0x11b0 net/bpf/test_run.c:1267 bpf_prog_test_run+0x33c/0x3b0 kernel/bpf/syscall.c:4240 __sys_bpf+0x48d/0x810 kernel/bpf/syscall.c:5649 __do_sys_bpf kernel/bpf/syscall.c:5738 [inline] __se_sys_bpf kernel/bpf/syscall.c:5736 [inline] __x64_sys_bpf+0x7c/0x90 kernel/bpf/syscall.c:5736 do_syscall_64+0xfd/0x240 entry_SYSCALL_64_after_hwframe+0x6d/0x75 RIP: 0033:0x7fe76247dda9 Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 e1 20 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:00007fe7632120c8 EFLAGS: 00000246 ORIG_RAX: 0000000000000141 RAX: ffffffffffffffda RBX: 00007fe7625abf80 RCX: 00007fe76247dda9 RDX: 0000000000000050 RSI: 0000000020000240 RDI: 000000000000000a RBP: 00007fe7624ca47a R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 000000000000000b R14: 00007fe7625abf80 R15: 00007ffcf8e59e58 </TASK> Modules linked in: ---[ end trace 0000000000000000 ]--- RIP: 0010:dev_map_enqueue+0x31/0x3e0 kernel/bpf/devmap.c:539 Code: 41 56 41 55 41 54 53 48 83 ec 18 49 89 d4 49 89 f5 48 89 fd 49 be 00 00 00 00 00 fc ff df e8 56 3a d8 ff 48 89 e8 48 c1 e8 03 <42> 80 3c 30 00 74 08 48 89 ef e8 60 89 3b 00 4c 8b 7d 00 48 83 c5 RSP: 0018:ffffc90010e6f688 EFLAGS: 00010256 RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000040000 RDX: ffffc9000fb19000 RSI: 0000000000000c96 RDI: 0000000000000c97 RBP: 0000000000000000 R08: 0000000000000005 R09: ffffffff8954502e R10: 0000000000000004 R11: ffff88805bde3c00 R12: ffff88807e182000 R13: ffff88805595d070 R14: dffffc0000000000 R15: ffff8880b953c288 FS: 00007fe7632126c0(0000) GS:ffff8880b9500000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000001b32d23000 CR3: 000000006b1cc000 CR4: 0000000000350ef0 ---------------- Code disassembly (best guess): 0: 41 56 push %r14 2: 41 55 push %r13 4: 41 54 push %r12 6: 53 push %rbx 7: 48 83 ec 18 sub $0x18,%rsp b: 49 89 d4 mov %rdx,%r12 e: 49 89 f5 mov %rsi,%r13 11: 48 89 fd mov %rdi,%rbp 14: 49 be 00 00 00 00 00 movabs $0xdffffc0000000000,%r14 1b: fc ff df 1e: e8 56 3a d8 ff call 0xffd83a79 23: 48 89 e8 mov %rbp,%rax 26: 48 c1 e8 03 shr $0x3,%rax * 2a: 42 80 3c 30 00 cmpb $0x0,(%rax,%r14,1) <-- trapping instruction 2f: 74 08 je 0x39 31: 48 89 ef mov %rbp,%rdi 34: e8 60 89 3b 00 call 0x3b8999 39: 4c 8b 7d 00 mov 0x0(%rbp),%r15 3d: 48 rex.W 3e: 83 .byte 0x83 3f: c5 .byte 0xc5 --- 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 syzkaller@...glegroups.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 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
Powered by blists - more mailing lists