[v6.1] BUG: unable to handle kernel NULL pointer dereference in bond_xdp_xmit

0 views
Skip to first unread message

syzbot

unread,
Apr 25, 2024, 3:36:26 PMApr 25
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 6741e066ec76 Linux 6.1.87
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1716af80980000
kernel config: https://syzkaller.appspot.com/x/.config?x=3fc2f61bd0ae457
dashboard link: https://syzkaller.appspot.com/bug?extid=eb9803c2147c3ba51ed1
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/665ba05da528/disk-6741e066.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/2ec8afc9ea0a/vmlinux-6741e066.xz
kernel image: https://storage.googleapis.com/syzbot-assets/b0dbfd69f35b/bzImage-6741e066.xz

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

BUG: kernel NULL pointer dereference, address: 0000000000000000
#PF: supervisor instruction fetch in kernel mode
#PF: error_code(0x0010) - not-present page
PGD 47b95067 P4D 47b95067 PUD 7e4e0067 PMD 0
Oops: 0010 [#1] PREEMPT SMP KASAN
CPU: 1 PID: 16105 Comm: syz-executor.4 Not tainted 6.1.87-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024
RIP: 0010:0x0
Code: Unable to access opcode bytes at 0xffffffffffffffd6.
RSP: 0018:ffffc9000310f358 EFLAGS: 00010246
RAX: 1ffffffff16e4ceb RBX: ffffffff8b726758 RCX: 0000000000000001
RDX: ffffc9000310f400 RSI: 0000000000000001 RDI: ffff8880216a8000
RBP: ffffc9000310f4d0 R08: ffffffff85a842f1 R09: ffffed10042d5008
R10: 0000000000000000 R11: dffffc0000000001 R12: dffffc0000000000
R13: ffff8880216a8000 R14: ffffc9000310f438 R15: ffffc9000310f438
FS: 00007f5ba9a7a6c0(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffffffffffffd6 CR3: 000000002acc2000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000600
Call Trace:
<TASK>
bond_xdp_xmit+0x3fd/0x650 drivers/net/bonding/bond_main.c:5546
bq_xmit_all+0xdb8/0x1210 kernel/bpf/devmap.c:389
__dev_flush+0xc9/0x1c0 kernel/bpf/devmap.c:419
xdp_do_flush+0xa/0x20 net/core/filter.c:4167
xdp_test_run_batch net/bpf/test_run.c:332 [inline]
bpf_test_run_xdp_live+0x1650/0x1ea0 net/bpf/test_run.c:362
bpf_prog_test_run_xdp+0x7d1/0x1130 net/bpf/test_run.c:1387
bpf_prog_test_run+0x32f/0x3a0 kernel/bpf/syscall.c:3670
__sys_bpf+0x3eb/0x6c0 kernel/bpf/syscall.c:5023
__do_sys_bpf kernel/bpf/syscall.c:5109 [inline]
__se_sys_bpf kernel/bpf/syscall.c:5107 [inline]
__x64_sys_bpf+0x78/0x90 kernel/bpf/syscall.c:5107
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7f5ba8c7dea9
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:00007f5ba9a7a0c8 EFLAGS: 00000246 ORIG_RAX: 0000000000000141
RAX: ffffffffffffffda RBX: 00007f5ba8dabf80 RCX: 00007f5ba8c7dea9
RDX: 0000000000000050 RSI: 00000000200000c0 RDI: 000000000000000a
RBP: 00007f5ba8cca4a4 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 000000000000000b R14: 00007f5ba8dabf80 R15: 00007ffcaa897238
</TASK>
Modules linked in:
CR2: 0000000000000000
---[ end trace 0000000000000000 ]---
RIP: 0010:0x0
Code: Unable to access opcode bytes at 0xffffffffffffffd6.
RSP: 0018:ffffc9000310f358 EFLAGS: 00010246
RAX: 1ffffffff16e4ceb RBX: ffffffff8b726758 RCX: 0000000000000001
RDX: ffffc9000310f400 RSI: 0000000000000001 RDI: ffff8880216a8000
RBP: ffffc9000310f4d0 R08: ffffffff85a842f1 R09: ffffed10042d5008
R10: 0000000000000000 R11: dffffc0000000001 R12: dffffc0000000000
R13: ffff8880216a8000 R14: ffffc9000310f438 R15: ffffc9000310f438
FS: 00007f5ba9a7a6c0(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffffffffffffd6 CR3: 000000002acc2000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000600


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