From: Mykyta Yatsenko <mykyta.yatsenko5@gmail.com>
To: Jenny Guanni Qu <qguanni@gmail.com>, bpf@vger.kernel.org
Cc: daniel@iogearbox.net, ast@kernel.org, andrii@kernel.org,
yonghong.song@linux.dev, lkp@intel.com
Subject: Re: [PATCH v4 1/2] bpf: Fix undefined behavior in interpreter sdiv/smod for INT_MIN
Date: Tue, 10 Mar 2026 00:28:27 +0000 [thread overview]
Message-ID: <86335845-ee95-4d7c-8208-f2bdd9cde90d@gmail.com> (raw)
In-Reply-To: <20260309215910.4131143-2-qguanni@gmail.com>
On 3/9/26 9:59 PM, Jenny Guanni Qu wrote:
> The BPF interpreter's signed 32-bit division and modulo handlers use
> the kernel abs() macro on s32 operands. The abs() macro documentation
> (include/linux/math.h) explicitly states the result is undefined when
> the input is the type minimum. When DST contains S32_MIN (0x80000000),
> abs((s32)DST) triggers undefined behavior and returns S32_MIN unchanged
> on arm64/x86. This value is then sign-extended to u64 as
> 0xFFFFFFFF80000000, causing do_div() to compute the wrong result.
>
> The verifier's abstract interpretation (scalar32_min_max_sdiv) computes
> the mathematically correct result for range tracking, creating a
> verifier/interpreter mismatch that can be exploited for out-of-bounds
> map value access.
>
> Introduce __safe_abs32() which handles S32_MIN correctly by casting
> to u32 before negating, avoiding signed overflow entirely. Replace
> all 8 abs((s32)...) call sites in the interpreter's sdiv32/smod32
> handlers.
>
> Fixes: ec0e2da95f72 ("bpf: Support new signed div/mod instructions.")
> Acked-by: Yonghong Song <yonghong.song@linux.dev>
> Signed-off-by: Jenny Guanni Qu <qguanni@gmail.com>
> ---
> kernel/bpf/core.c | 22 ++++++++++++++--------
> 1 file changed, 14 insertions(+), 8 deletions(-)
>
Acked-by: Mykyta Yatsenko <yatsenko@meta.com>
> diff --git a/kernel/bpf/core.c b/kernel/bpf/core.c
> index 3ece2da55625..a620d4d6f567 100644
> --- a/kernel/bpf/core.c
> +++ b/kernel/bpf/core.c
> @@ -1736,6 +1736,12 @@ bool bpf_opcode_in_insntable(u8 code)
> }
>
> #ifndef CONFIG_BPF_JIT_ALWAYS_ON
> +/* Safe absolute value for s32 to prevent undefined behavior for abs(S32_MIN) */
> +static inline u32 __safe_abs32(s32 x)
> +{
> + return x >= 0 ? (u32)x : -(u32)x;
> +}
> +
> /**
> * ___bpf_prog_run - run eBPF program on a given context
> * @regs: is the array of MAX_BPF_EXT_REG eBPF pseudo-registers
> @@ -1900,8 +1906,8 @@ static u64 ___bpf_prog_run(u64 *regs, const struct bpf_insn *insn)
> DST = do_div(AX, (u32) SRC);
> break;
> case 1:
> - AX = abs((s32)DST);
> - AX = do_div(AX, abs((s32)SRC));
> + AX = __safe_abs32((s32)DST);
> + AX = do_div(AX, __safe_abs32((s32)SRC));
> if ((s32)DST < 0)
> DST = (u32)-AX;
> else
> @@ -1928,8 +1934,8 @@ static u64 ___bpf_prog_run(u64 *regs, const struct bpf_insn *insn)
> DST = do_div(AX, (u32) IMM);
> break;
> case 1:
> - AX = abs((s32)DST);
> - AX = do_div(AX, abs((s32)IMM));
> + AX = __safe_abs32((s32)DST);
> + AX = do_div(AX, __safe_abs32((s32)IMM));
> if ((s32)DST < 0)
> DST = (u32)-AX;
> else
> @@ -1955,8 +1961,8 @@ static u64 ___bpf_prog_run(u64 *regs, const struct bpf_insn *insn)
> DST = (u32) AX;
> break;
> case 1:
> - AX = abs((s32)DST);
> - do_div(AX, abs((s32)SRC));
> + AX = __safe_abs32((s32)DST);
> + do_div(AX, __safe_abs32((s32)SRC));
> if (((s32)DST < 0) == ((s32)SRC < 0))
> DST = (u32)AX;
> else
> @@ -1982,8 +1988,8 @@ static u64 ___bpf_prog_run(u64 *regs, const struct bpf_insn *insn)
> DST = (u32) AX;
> break;
> case 1:
> - AX = abs((s32)DST);
> - do_div(AX, abs((s32)IMM));
> + AX = __safe_abs32((s32)DST);
> + do_div(AX, __safe_abs32((s32)IMM));
> if (((s32)DST < 0) == ((s32)IMM < 0))
> DST = (u32)AX;
> else
next prev parent reply other threads:[~2026-03-10 0:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-09 21:59 [PATCH v4 0/2] bpf: Fix abs(INT_MIN) undefined behavior in interpreter sdiv/smod Jenny Guanni Qu
2026-03-09 21:59 ` [PATCH v4 1/2] bpf: Fix undefined behavior in interpreter sdiv/smod for INT_MIN Jenny Guanni Qu
2026-03-10 0:28 ` Mykyta Yatsenko [this message]
2026-03-10 19:03 ` Alexei Starovoitov
2026-03-09 21:59 ` [PATCH v4 2/2] selftests/bpf: Add tests for sdiv32/smod32 with INT_MIN dividend Jenny Guanni Qu
2026-03-10 2:05 ` Jiayuan Chen
2026-03-10 2:20 ` Yonghong Song
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=86335845-ee95-4d7c-8208-f2bdd9cde90d@gmail.com \
--to=mykyta.yatsenko5@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=lkp@intel.com \
--cc=qguanni@gmail.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