bpf: Fix array bounds error with may_goto
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
bpf: Fix array bounds error with may_goto
may_goto uses an additional 8 bytes on the stack, which causes the interpreters[] array to go out of bounds when calculating index by stack_size.
1. If a BPF program is rewritten, re-evaluate the stack size. For non-JIT cases, reject loading directly.
2. For non-JIT cases, calculating interpreters[idx] may still cause out-of-bounds array access, and just warn about it.
3. For jit_requested cases, the execution of bpf_func also needs to be warned. So move the definition of function __bpf_prog_ret0_warn out of the macro definition CONFIG_BPF_JIT_ALWAYS_ON.
From the CVE record · Linux
The Linux kernel’s BPF may_goto handling can calculate an out-of-bounds index into the interpreters array because may_goto uses an additional eight bytes of stack. This can cause an out-of-bounds array access when a BPF program is loaded; the input does not specify attacker access requirements or whether user interaction is needed.
Engineers running the Linux kernel should check their BPF exposure; affected versions are not specified.