From: syzbot <syzbot+33f4297b5f927648741a@syzkaller.appspotmail.com>
To: eadavis@qq.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [bpf?] UBSAN: array-index-out-of-bounds in check_stack_range_initialized
Date: Wed, 20 Mar 2024 01:02:03 -0700 [thread overview]
Message-ID: <0000000000008f8e88061413011f@google.com> (raw)
In-Reply-To: <tencent_79DD6EEACCA727D846F212CE8679C998EE06@qq.com>
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
UBSAN: array-index-out-of-bounds in check_stack_range_initialized
mio: -8, mao: -8, as: -2147483647, check_stack_range_initialized
------------[ cut here ]------------
UBSAN: array-index-out-of-bounds in kernel/bpf/verifier.c:7193:12
index -1 is out of range for type 'u8[8]' (aka 'unsigned char[8]')
CPU: 0 PID: 5496 Comm: syz-executor.0 Not tainted 6.8.0-syzkaller-05230-g114b5b3b4bde-dirty #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/29/2024
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x1e7/0x2e0 lib/dump_stack.c:106
ubsan_epilogue lib/ubsan.c:217 [inline]
__ubsan_handle_out_of_bounds+0x121/0x150 lib/ubsan.c:415
check_stack_range_initialized+0x13d8/0x1630 kernel/bpf/verifier.c:7193
check_helper_mem_access+0x2eb/0xfa0 kernel/bpf/verifier.c:7297
check_helper_call+0x263c/0x7220 kernel/bpf/verifier.c:10255
do_check+0x9e29/0x10530 kernel/bpf/verifier.c:17804
do_check_common+0x14bd/0x1dd0 kernel/bpf/verifier.c:20503
do_check_main kernel/bpf/verifier.c:20594 [inline]
bpf_check+0x136ab/0x19010 kernel/bpf/verifier.c:21264
bpf_prog_load+0x1667/0x20f0 kernel/bpf/syscall.c:2895
__sys_bpf+0x4ee/0x810 kernel/bpf/syscall.c:5631
__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+0xfb/0x240
entry_SYSCALL_64_after_hwframe+0x6d/0x75
RIP: 0033:0x7fb440a7dda9
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:00007fb4417ef0c8 EFLAGS: 00000246 ORIG_RAX: 0000000000000141
RAX: ffffffffffffffda RBX: 00007fb440babf80 RCX: 00007fb440a7dda9
RDX: 0000000000000090 RSI: 00000000200000c0 RDI: 0000000000000005
RBP: 00007fb440aca47a R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 000000000000000b R14: 00007fb440babf80 R15: 00007ffc0626c2f8
</TASK>
---[ end trace ]---
Tested on:
commit: 114b5b3b bpf, arm64: fix bug in BPF_LDX_MEMSX
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf.git master
console output: https://syzkaller.appspot.com/x/log.txt?x=14084006180000
kernel config: https://syzkaller.appspot.com/x/.config?x=6fb1be60a193d440
dashboard link: https://syzkaller.appspot.com/bug?extid=33f4297b5f927648741a
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
patch: https://syzkaller.appspot.com/x/patch.diff?x=16c4aa31180000
next prev parent reply other threads:[~2024-03-20 8:02 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-19 18:12 [syzbot] [bpf?] UBSAN: array-index-out-of-bounds in check_stack_range_initialized syzbot
2024-03-20 0:33 ` Edward Adam Davis
2024-03-20 8:02 ` syzbot [this message]
2024-03-20 9:40 ` Edward Adam Davis
2024-03-20 10:09 ` syzbot
2024-03-20 11:17 ` Edward Adam Davis
2024-03-20 19:53 ` syzbot
2024-03-20 23:52 ` Edward Adam Davis
2024-03-21 14:39 ` syzbot
2024-03-21 7:33 ` stack access issue. " Alexei Starovoitov
2024-03-21 14:07 ` Andrei Matei
2024-03-24 0:50 ` Andrei Matei
2024-03-24 0:52 ` Alexei Starovoitov
2024-03-24 2:12 ` Andrei Matei
2024-03-24 2:55 ` Alexei Starovoitov
2024-03-26 2:48 ` Andrei Matei
2024-03-22 0:11 ` Edward Adam Davis
2024-03-22 10:42 ` syzbot
2024-03-23 4:42 ` Edward Adam Davis
2024-03-23 9:08 ` syzbot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0000000000008f8e88061413011f@google.com \
--to=syzbot+33f4297b5f927648741a@syzkaller.appspotmail.com \
--cc=eadavis@qq.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.