bpf: fix check for attempt to corrupt spilled pointer
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 27113c59b6d0a587b29ae72d4ff3f832f58b0651 · < ab125ed3ec1c10ccc36bc98c7a4256ad114a3dae| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
bpf: fix check for attempt to corrupt spilled pointer
When register is spilled onto a stack as a 1/2/4-byte register, we set slot_type[BPF_REG_SIZE - 1] (plus potentially few more below it, depending on actual spill size). So to check if some stack slot has spilled register we need to consult slot_type[7], not slot_type[0].
To avoid the need to remember and double-check this in the future, just use is_spilled_reg() helper.
From the CVE record · Linux
The Linux kernel’s BPF stack-slot check looks at the wrong byte when checking for a spilled register. This can let an attempt to corrupt a spilled pointer evade that check. The input does not specify whether exploitation requires local or network access, authentication, or user interaction.
Engineers running Linux kernels with BPF should check their exposure; affected versions are not specified.