Linux
bpf: Don't predict JMP32 pointer vs zero comparisons
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 ...'.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= cac616db39c207dc63465a4e05c6ce0e60b2cce4, < 6e1544986536734166176c3add504add23bcbd15
- >= cac616db39c207dc63465a4e05c6ce0e60b2cce4, < d16f0eafcaa62e677a2b5b0dabc1f8d31dfe3d4d
- >= cac616db39c207dc63465a4e05c6ce0e60b2cce4, < e2ae33247e8b2dbe9d116d3e61cadf6d548339c6
- >= cac616db39c207dc63465a4e05c6ce0e60b2cce4, < a4d7f94c1ca914469ced665ec2f98be669aef462
- >= cac616db39c207dc63465a4e05c6ce0e60b2cce4, < e51179a4e09846f8fd0f26a05068520de2b301bf
Fixed in 6e1544986536734166176c3add504add23bcbd15, d16f0eafcaa62e677a2b5b0dabc1f8d31dfe3d4d, e2ae33247e8b2dbe9d116d3e61cadf6d548339c6, a4d7f94c1ca914469ced665ec2f98be669aef462, e51179a4e09846f8fd0f26a05068520de2b301bf
- 5.8
Fixed in 0, 6.6.160, 6.12.111, 6.18.53, 7.2.7, 7.3
Mitigation
Upgrade Linux to 6e1544986536734166176c3add504add23bcbd15 or d16f0eafcaa62e677a2b5b0dabc1f8d31dfe3d4d or e2ae33247e8b2dbe9d116d3e61cadf6d548339c6 or a4d7f94c1ca914469ced665ec2f98be669aef462 or e51179a4e09846f8fd0f26a05068520de2b301bf or later.
Upgrade Linux to 0 or 6.6.160 or 6.12.111 or 6.18.53 or 7.2.7 or 7.3 or later.
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.