From: patchwork-bot+netdevbpf@kernel.org
To: Guanni Qu <qguanni@gmail.com>
Cc: bpf@vger.kernel.org, daniel@iogearbox.net, ast@kernel.org,
andrii@kernel.org, mykyta.yatsenko5@gmail.com,
yonghong.song@linux.dev, jiayuan.chen@linux.dev, lkp@intel.com
Subject: Re: [PATCH v5 0/2] bpf: Fix abs(INT_MIN) undefined behavior in interpreter sdiv/smod
Date: Sat, 21 Mar 2026 20:20:11 +0000 [thread overview]
Message-ID: <177412441129.2951219.8888701346937198649.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260311011116.2108005-1-qguanni@gmail.com>
Hello:
This series was applied to bpf/bpf.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Wed, 11 Mar 2026 01:11:14 +0000 you wrote:
> The BPF interpreter's signed 32-bit division and modulo handlers use
> abs() on s32 operands, which is undefined for S32_MIN. This causes
> the interpreter to compute wrong results, creating a mismatch with
> the verifier's range tracking.
>
> For example, INT_MIN / 2 returns 0x40000000 instead of the correct
> 0xC0000000. The verifier tracks the correct range, so a crafted BPF
> program can exploit the mismatch for out-of-bounds map value access
> (confirmed by KASAN).
>
> [...]
Here is the summary with links:
- [v5,1/2] bpf: Fix undefined behavior in interpreter sdiv/smod for INT_MIN
https://git.kernel.org/bpf/bpf/c/c77b30bd1dcb
- [v5,2/2] selftests/bpf: Add tests for sdiv32/smod32 with INT_MIN dividend
https://git.kernel.org/bpf/bpf/c/4ac95c65efea
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:[~2026-03-21 20:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-11 1:11 [PATCH v5 0/2] bpf: Fix abs(INT_MIN) undefined behavior in interpreter sdiv/smod Jenny Guanni Qu
2026-03-11 1:11 ` [PATCH v5 1/2] bpf: Fix undefined behavior in interpreter sdiv/smod for INT_MIN Jenny Guanni Qu
2026-03-11 1:11 ` [PATCH v5 2/2] selftests/bpf: Add tests for sdiv32/smod32 with INT_MIN dividend Jenny Guanni Qu
2026-03-21 20:20 ` 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=177412441129.2951219.8888701346937198649.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=jiayuan.chen@linux.dev \
--cc=lkp@intel.com \
--cc=mykyta.yatsenko5@gmail.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