Re: [PATCH bpf-next 1/2] bpf: Enforce regsafe base id consistency for BPF_ADD_CONST scalars

[patchwork-bot+netdevbpf@kernel.org]

Hello:

This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:

On Sat, 11 Apr 2026 01:26:50 +0200 you wrote:
> When regsafe() compares two scalar registers that both carry
> BPF_ADD_CONST, check_scalar_ids() maps their full compound id
> (aka base | BPF_ADD_CONST flag) as one idmap entry. However,
> it never verifies that the underlying base ids, that is, with
> the flag stripped are consistent with existing idmap mappings.
> 
> This allows construction of two verifier states where the old
> state has R3 = R2 + 10 (both sharing base id A) while the current
> state has R3 = R4 + 10 (base id C, unrelated to R2). The idmap
> creates two independent entries: A->B (for R2) and A|flag->C|flag
> (for R3), without catching that A->C conflicts with A->B. State
> pruning then incorrectly succeeds.
> 
> [...]

Here is the summary with links:
  - [bpf-next,1/2] bpf: Enforce regsafe base id consistency for BPF_ADD_CONST scalars
    https://git.kernel.org/bpf/bpf-next/c/2f2ec8e7730e
  - [bpf-next,2/2] selftests/bpf: Add test for add_const base_id consistency
    https://git.kernel.org/bpf/bpf-next/c/497fa510ee46

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html