From: patchwork-bot+netdevbpf@kernel.org
To: Yonghong Song <yonghong.song@linux.dev>
Cc: bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
daniel@iogearbox.net, kernel-team@fb.com, martin.lau@kernel.org,
syzbot+3758842a6c01012aa73b@syzkaller.appspotmail.com
Subject: Re: [PATCH bpf-next] kernel/bpf: Fix an array-index-out-of-bounds issue in disasm.c
Date: Tue, 01 Aug 2023 00:40:20 +0000 [thread overview]
Message-ID: <169085042006.2613.6575059402578434436.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230731204534.1975311-1-yonghong.song@linux.dev>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Mon, 31 Jul 2023 13:45:34 -0700 you wrote:
> syzbot reported an array-index-out-of-bounds when printing out bpf
> insns. Further investigation shows the insn is illegal but
> is printed out due to log level 1 or 2 before actual insn verification
> in do_check().
>
> This particular illegal insn is a MOVSX insn with offset value 2.
> The legal offset value for MOVSX should be 8, 16 and 32.
> The disasm sign-extension-size array index is calculated as
> (insn->off / 8) - 1
> and offset value 2 gives an out-of-bound index -1.
>
> [...]
Here is the summary with links:
- [bpf-next] kernel/bpf: Fix an array-index-out-of-bounds issue in disasm.c
https://git.kernel.org/bpf/bpf-next/c/e99688eba2e9
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2023-08-01 0:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-31 20:45 [PATCH bpf-next] kernel/bpf: Fix an array-index-out-of-bounds issue in disasm.c Yonghong Song
2023-07-31 22:03 ` Eduard Zingerman
2023-08-01 0:37 ` Alexei Starovoitov
2023-08-01 0:39 ` Yonghong Song
2023-08-01 0:40 ` patchwork-bot+netdevbpf [this message]
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=169085042006.2613.6575059402578434436.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=kernel-team@fb.com \
--cc=martin.lau@kernel.org \
--cc=syzbot+3758842a6c01012aa73b@syzkaller.appspotmail.com \
--cc=yonghong.song@linux.dev \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox