From: Eduard Zingerman <eddyz87@gmail.com>
To: Yonghong Song <yonghong.song@linux.dev>, bpf@vger.kernel.org
Cc: Alexei Starovoitov <ast@kernel.org>,
Andrii Nakryiko <andrii@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
kernel-team@fb.com, Martin KaFai Lau <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 01:03:26 +0300 [thread overview]
Message-ID: <14e9b56db903b80d9c2ee7ccc1fbe7d795a26327.camel@gmail.com> (raw)
In-Reply-To: <20230731204534.1975311-1-yonghong.song@linux.dev>
On Mon, 2023-07-31 at 13:45 -0700, Yonghong Song 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.
>
> Tighten the checking for MOVSX insn in disasm.c to avoid
> array-index-out-of-bounds issue.
>
> Reported-by: syzbot+3758842a6c01012aa73b@syzkaller.appspotmail.com
> Fixes: f835bb622299 ("bpf: Add kernel/bpftool asm support for new instructions")
> Signed-off-by: Yonghong Song <yonghong.song@linux.dev>
Acked-by: Eduard Zingerman <eddyz87@gmail.com>
> ---
> kernel/bpf/disasm.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/kernel/bpf/disasm.c b/kernel/bpf/disasm.c
> index d7bff608f299..ef7c107c7b8f 100644
> --- a/kernel/bpf/disasm.c
> +++ b/kernel/bpf/disasm.c
> @@ -162,7 +162,8 @@ static bool is_sdiv_smod(const struct bpf_insn *insn)
>
> static bool is_movsx(const struct bpf_insn *insn)
> {
> - return BPF_OP(insn->code) == BPF_MOV && insn->off != 0;
> + return BPF_OP(insn->code) == BPF_MOV &&
> + (insn->off == 8 || insn->off == 16 || insn->off == 32);
> }
>
> void print_bpf_insn(const struct bpf_insn_cbs *cbs,
next prev parent reply other threads:[~2023-07-31 22:03 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 [this message]
2023-08-01 0:37 ` Alexei Starovoitov
2023-08-01 0:39 ` Yonghong Song
2023-08-01 0:40 ` patchwork-bot+netdevbpf
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=14e9b56db903b80d9c2ee7ccc1fbe7d795a26327.camel@gmail.com \
--to=eddyz87@gmail.com \
--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