All reports
Medium

kernel: bpf: Don't predict JMP32 pointer vs zero comparisons

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
Affected versions
Unknown
Fixed version
Not reported

Exploitation

CVE-2026-98041

Probability of exploitation in the next 30 days: 0.15%

FIRST EPSS · 2026-11-20

Description

In the Linux kernel, the following vulnerability has been resolved: bpf: Don't predict JMP32 pointer vs zero comparisons Consider the following program: r1 = map_value; /* low 32 bits are zero at runtime */ r6 = 0xdead000000000000; if w1 != 0 goto l1; l0: r1 += r6; r2 = *(u64 *)(r1 + 0); exit; l1: r6 = 0; goto l0; At the moment is_branch_taken() reports the jump as always taken, because it does not distinguish between BPF_JMP and BPF_JMP32 comparisons when processing 'if w1 != 0 ...'.

A flaw was found in the Linux kernel's Berkeley Packet Filter (BPF) verifier. The verifier incorrectly predicts that 32-bit conditional branch comparisons between a pointer and zero are always taken, failing to account for valid pointer values whose lower 32 bits can be zero. A local attacker could exploit this vulnerability by loading a specially crafted BPF program to bypass safety checks, potentially resulting in out-of-bounds kernel memory access and local privilege escalation.