From: KaFai Wan <kafai.wan@linux.dev>
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>
Cc: Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
John Fastabend <john.fastabend@gmail.com>,
Andrii Nakryiko <andrii@kernel.org>,
Martin KaFai Lau <martin.lau@linux.dev>,
Eduard <eddyz87@gmail.com>, Song Liu <song@kernel.org>,
Yonghong Song <yonghong.song@linux.dev>,
KP Singh <kpsingh@kernel.org>,
Stanislav Fomichev <sdf@fomichev.me>,
Hao Luo <haoluo@google.com>, Jiri Olsa <jolsa@kernel.org>,
Shuah Khan <shuah@kernel.org>,
Paul Chaignon <paul.chaignon@gmail.com>,
Matan Shachnai <m.shachnai@gmail.com>,
Henriette Herzog <henriette.herzog@rub.de>,
Luis Gerhorst <luis.gerhorst@fau.de>,
Harishankar Vishwanathan <harishankar.vishwanathan@gmail.com>,
colin.i.king@gmail.com, bpf <bpf@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
"open list:KERNEL SELFTEST FRAMEWORK"
<linux-kselftest@vger.kernel.org>,
Kaiyan Mei <M202472210@hust.edu.cn>,
Yinhao Hu <dddddd@hust.edu.cn>
Subject: Re: [PATCH bpf-next v3 1/2] bpf: Skip bounds adjustment for conditional jumps on same scalar register
Date: Mon, 03 Nov 2025 14:23:21 +0800 [thread overview]
Message-ID: <7df70d3be4043296471f3cd3267898f953985d9a.camel@linux.dev> (raw)
In-Reply-To: <CAADnVQ+4QoCU4gYEfTR6Ok122zkfG32s8AxRx-irMcCA1jEhvQ@mail.gmail.com>
On Fri, 2025-10-31 at 09:37 -0700, Alexei Starovoitov wrote:
> On Fri, Oct 31, 2025 at 8:44 AM KaFai Wan <kafai.wan@linux.dev> wrote:
> >
> > When conditional jumps are performed on the same scalar register
> > (e.g., r0 <= r0, r0 > r0, r0 < r0), the BPF verifier incorrectly
> > attempts to adjust the register's min/max bounds. This leads to
> > invalid range bounds and triggers a BUG warning.
> >
> > The problematic BPF program:
> > 0: call bpf_get_prandom_u32
> > 1: w8 = 0x80000000
> > 2: r0 &= r8
> > 3: if r0 > r0 goto <exit>
> >
> > The instruction 3 triggers kernel warning:
> > 3: if r0 > r0 goto <exit>
> > true_reg1: range bounds violation u64=[0x1, 0x0] s64=[0x1, 0x0] u32=[0x1, 0x0] s32=[0x1, 0x0]
> > var_off=(0x0, 0x0)
> > true_reg2: const tnum out of sync with range bounds u64=[0x0, 0xffffffffffffffff]
> > s64=[0x8000000000000000, 0x7fffffffffffffff] var_off=(0x0, 0x0)
> >
> > Comparing a register with itself should not change its bounds and
> > for most comparison operations, comparing a register with itself has
> > a known result (e.g., r0 == r0 is always true, r0 < r0 is always false).
> >
> > Fix this by:
> > 1. Enhance is_scalar_branch_taken() to properly handle branch direction
> > computation for same register comparisons across all BPF jump operations
> > 2. Adds early return in reg_set_min_max() to avoid bounds adjustment
> > for unknown branch directions (e.g., BPF_JSET) on the same register
> >
> > The fix ensures that unnecessary bounds adjustments are skipped, preventing
> > the verifier bug while maintaining correct branch direction analysis.
> >
> > Reported-by: Kaiyan Mei <M202472210@hust.edu.cn>
> > Reported-by: Yinhao Hu <dddddd@hust.edu.cn>
> > Closes: https://lore.kernel.org/all/1881f0f5.300df.199f2576a01.Coremail.kaiyanm@hust.edu.cn/
> > Signed-off-by: KaFai Wan <kafai.wan@linux.dev>
> > ---
> > kernel/bpf/verifier.c | 33 +++++++++++++++++++++++++++++++++
> > 1 file changed, 33 insertions(+)
> >
> > diff --git a/kernel/bpf/verifier.c b/kernel/bpf/verifier.c
> > index 542e23fb19c7..a571263f4ebe 100644
> > --- a/kernel/bpf/verifier.c
> > +++ b/kernel/bpf/verifier.c
> > @@ -15995,6 +15995,8 @@ static int is_scalar_branch_taken(struct bpf_reg_state *reg1, struct
> > bpf_reg_sta
> >
> > switch (opcode) {
> > case BPF_JEQ:
> > + if (reg1 == reg2)
> > + return 1;
> > /* constants, umin/umax and smin/smax checks would be
> > * redundant in this case because they all should match
> > */
> > @@ -16021,6 +16023,8 @@ static int is_scalar_branch_taken(struct bpf_reg_state *reg1, struct
> > bpf_reg_sta
> > }
> > break;
> > case BPF_JNE:
> > + if (reg1 == reg2)
> > + return 0;
> > /* constants, umin/umax and smin/smax checks would be
> > * redundant in this case because they all should match
> > */
> > @@ -16047,6 +16051,12 @@ static int is_scalar_branch_taken(struct bpf_reg_state *reg1, struct
> > bpf_reg_sta
> > }
> > break;
> > case BPF_JSET:
> > + if (reg1 == reg2) {
> > + if (tnum_is_const(t1))
> > + return t1.value != 0;
> > + else
> > + return (smin1 <= 0 && smax1 >= 0) ? -1 : 1;
> > + }
> > if (!is_reg_const(reg2, is_jmp32)) {
> > swap(reg1, reg2);
> > swap(t1, t2);
> > @@ -16059,48 +16069,64 @@ static int is_scalar_branch_taken(struct bpf_reg_state *reg1, struct
> > bpf_reg_sta
> > return 0;
> > break;
> > case BPF_JGT:
> > + if (reg1 == reg2)
> > + return 0;
> > if (umin1 > umax2)
> > return 1;
> > else if (umax1 <= umin2)
> > return 0;
> > break;
> > case BPF_JSGT:
> > + if (reg1 == reg2)
> > + return 0;
>
> This is uglier than the previous version.
> reg1 == reg2 is a syzbot territory.
> We shouldn't uglify the code everywhere because of it.
>
ok, will update in v4.
> pw-bot: cr
--
Thanks,
KaFai
next prev parent reply other threads:[~2025-11-03 6:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-31 15:41 [PATCH bpf-next v3 0/2] bpf: Skip bounds adjustment for conditional jumps on same scalar register KaFai Wan
2025-10-31 15:41 ` [PATCH bpf-next v3 1/2] " KaFai Wan
2025-10-31 16:37 ` Alexei Starovoitov
2025-11-03 6:23 ` KaFai Wan [this message]
2025-10-31 15:41 ` [PATCH bpf-next v3 2/2] selftests/bpf: Add test " KaFai Wan
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=7df70d3be4043296471f3cd3267898f953985d9a.camel@linux.dev \
--to=kafai.wan@linux.dev \
--cc=M202472210@hust.edu.cn \
--cc=alexei.starovoitov@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=colin.i.king@gmail.com \
--cc=daniel@iogearbox.net \
--cc=dddddd@hust.edu.cn \
--cc=eddyz87@gmail.com \
--cc=haoluo@google.com \
--cc=harishankar.vishwanathan@gmail.com \
--cc=henriette.herzog@rub.de \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=luis.gerhorst@fau.de \
--cc=m.shachnai@gmail.com \
--cc=martin.lau@linux.dev \
--cc=paul.chaignon@gmail.com \
--cc=sdf@fomichev.me \
--cc=shuah@kernel.org \
--cc=song@kernel.org \
--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