bpf: Restrict CO-RE poisoning to relocatable instructions
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ d7a252708dbc950ca2064310217e8b9f85846e2f · < 8e4cbcca1e0a2fc5e6c8edb68e0cf5f2587f9319| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
bpf: Restrict CO-RE poisoning to relocatable instructions
CO-RE relocation records can name any instruction offset. When a relocation cannot be resolved, bpf_core_patch_insn() currently poisons its target before checking whether that instruction is a valid relocation target. Malformed metadata can therefore replace jumps, calls, exits, register-source arithmetic, or non-immediate loads instead of failing at the relocation step.
Handle poisoning only after the instruction has passed the same class and operand-form checks used for a resolved relocation. Route invalid forms through the existing diagnostic and return a hard error. Keep poisoning supported instructions, including both halves of a plain ldimm64, so an unresolved relocation in dead code remains valid.
Extend bpf_core_poison_insn() to poison both halves of ldimm64, and return its status directly from each validated instruction case. This avoids routing the success path through a common label and leaves the helper free to report errors.
The shared relocation code applies this restriction to both libbpf and in-kernel CO-RE.
From the CVE record · Linux
Linux BPF CO-RE relocation handling can poison an invalid instruction target when a relocation cannot be resolved. Malformed relocation metadata can replace jumps, calls, exits, and other instructions instead of causing a relocation error. The input does not specify the attacker access or user interaction required.
Engineers running Linux kernels or libbpf with CO-RE relocation support should check their installations; affected versions are not specified.