Refuse CO-RE relocations for a signed program
Status from this message: This series was applied to bpf/bpf-next.git (master)
Get series with b4
b4 am [email protected]Versions newest first
Patches in v1 All 2 applied
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | bpf: Refuse CO-RE relocations for a signed programkernel/ | +9 | 1 reply | Applied |
| 2/2 | selftests/bpf: Test that a signed program with CO-RE relocations is refusedtools/ | +46 | 1 reply | Applied |
Reviews trailers per patch
All 2 patches have a Reviewed-by or Acked-by.
| Patch | Daniel Borkmann |
|---|---|
| 1/2 | A-b |
| 2/2 | A-b |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [PATCH bpf-next v1 0/2] Refuse CO-RE relocations for a signed program
The signature of a BPF program is checked over the insns as submitted, but the loader may also hand in CO-RE relocation records, which the kernel applies to those insns afterwards with values the loader picks through its BTF. Whoever holds a signed program can so change its constants once the signature has passed. Refuse relocations on a signed load, before the signature is examined, and test it.
Found by Sashiko on the "Fix some arena paper cuts" series:
https://lore.kernel.org/bpf/[email protected]/
Kumar Kartikeya Dwivedi (2):
bpf: Refuse CO-RE relocations for a signed program selftests/bpf: Test that a signed program with CO-RE relocations is
refused
kernel/bpf/verifier.c | 9 ++++ .../selftests/bpf/prog_tests/signed_loader.c | 46 +++++++++++++++++++ 2 files changed, 55 insertions(+)
base-commit: 25bb03f0a47b622b9025a1558bf2095ec1f55d26
Signature · 1 line
2.53.0-Meta