bpf: consider that tail calls invalidate packet pointers
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 1a4607ffba35bf2a630aab299e34dd3f6e658d70, Kernel 1c2244437f9ad3dd91215f920401a14f2542dbfc and Kernel f1692ee23dcaaddc24ba407b269707ee5df1301f.
In the Linux kernel, the following vulnerability has been resolved: bpf: consider that tail calls invalidate packet pointers Tail-called programs could execute any of the helpers that invalidate packet pointers. Hence, conservatively assume that each tail call invalidates packet pointers. Making the change in bpf_helper_changes_pkt_data() automatically makes use of check_cfg() logic that computes 'changes_pkt_data' effect for global sub-programs, such that the following program could be rejected: int tail_call(struct __sk_buff *sk) { bpf_tail_call_static(sk, &jmp_table, 0); return 0; } SEC("tc") int not_safe(struct __sk_buff *sk) { int *p = (void *)(long)sk->data; ... make p valid ... tail_call(sk); *p = 42; /* this is unsafe */ ... } The tc_bpf2bpf.c:subprog_tc() needs change: mark it as a function that can invalidate packet pointers. Otherwise, it can't be freplaced with tailcall_freplace.c:entry_freplace() that does a tail call.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =5.6, >=51c39bb1d5d105a02e29aa7960f0a395086e6342 <1a4607ffba35bf2a630aab299e34dd3f6e658d70, >=51c39bb1d5d105a02e29aa7960f0a395086e6342 <1c2244437f9ad3dd91215f920401a14f2542dbfc, >=51c39bb1d5d105a02e29aa7960f0a395086e6342 <f1692ee23dcaaddc24ba407b269707ee5df1301f | 1a4607ffba35bf2a630aab299e34dd3f6e658d70, 1c2244437f9ad3dd91215f920401a14f2542dbfc, f1692ee23dcaaddc24ba407b269707ee5df1301f |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket