All reports
Medium

kernel: bpf: Reset register ID for BPF_END value tracking

Affected versions

Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported

Exploitation

CVE-2026-43070

Probability of exploitation in the next 30 days: 0.12%

FIRST EPSS · 2026-11-21

Description

In the Linux kernel, the following vulnerability has been resolved: bpf: Reset register ID for BPF_END value tracking When a register undergoes a BPF_END (byte swap) operation, its scalar value is mutated in-place. If this register previously shared a scalar ID with another register (e.g., after an r1 = r0 assignment), this tie must be broken. Currently, the verifier misses resetting dst_reg->id to 0 for BPF_END. Consequently, if a conditional jump checks the swapped register, the verifier incorrectly propagates the learned bounds to the linked register, leading to false confidence in the linked register's value and potentially allowing out-of-bounds memory accesses. Fix this by explicitly resetting dst_reg->id to 0 in the BPF_END case to break the scalar tie, similar to how BPF_NEG handles it via __mark_reg_known.

A flaw was found in the Linux kernel's BPF (Berkeley Packet Filter) verifier. The verifier fails to correctly reset a register's ID after a BPF_END (byte swap) operation. This oversight can lead to the verifier incorrectly propagating learned memory bounds to other registers, creating false confidence in their values. Consequently, this could enable an attacker to perform out-of-bounds memory accesses, potentially leading to system instability or privilege escalation.