bpf: Remove tst_run from lwt_seg6local_prog_ops.
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 004d4b274e2a1a895a0e5dc66158b90a7d463d44 · < c13fda93aca118b8e5cd202e339046728ee7dddb| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
bpf: Remove tst_run from lwt_seg6local_prog_ops.
The syzbot reported that the lwt_seg6 related BPF ops can be invoked via bpf_test_run() without without entering input_action_end_bpf() first.
Martin KaFai Lau said that self test for BPF_PROG_TYPE_LWT_SEG6LOCAL probably didn't work since it was introduced in commit 04d4b274e2a ("ipv6: sr: Add seg6local action End.BPF"). The reason is that the per-CPU variable seg6_bpf_srh_states::srh is never assigned in the self test case but each BPF function expects it.
Remove test_run for BPF_PROG_TYPE_LWT_SEG6LOCAL.
From the CVE record · Linux
The Linux kernel allows lwt_seg6-related BPF operations to be invoked through bpf_test_run() without first entering input_action_end_bpf(). A caller able to use bpf_test_run() can reach these operations while the per-CPU state they expect has not been assigned; the input does not specify authentication requirements or user interaction.
Engineers running the Linux kernel should check their vendor advisory for affected versions; none are listed in the input.