History

xdp: fix cpumap redirect SKB creation bug

We want to avoid leaking pointer info from xdp_frame (that is placed in top of frame) like commit 6dfb970d3dbd ("xdp: avoid leaking info stored in frame data on page reuse"), and followup commit 97e19cce05e5 ("bpf: reserve xdp_frame size in xdp headroom") that reserve this headroom. These changes also affected how cpumap constructed SKBs, as xdpf->headroom size changed, the skb data starting point were in-effect shifted with 32 bytes (sizeof xdp_frame). This was still okay, as the cpumap frame_size calculation also included xdpf->headroom which were reduced by same amount. A bug was introduced in commit 77ea5f4cbe20 ("bpf/cpumap: make sure frame_size for build_skb is aligned if headroom isn't"), where the xdpf->headroom became part of the SKB_DATA_ALIGN rounding up. This round-up to find the frame_size is in principle still correct as it does not exceed the 2048 bytes frame_size (which is max for ixgbe and i40e), but the 32 bytes offset of pkt_data_start puts this over the 2048 bytes limit. This cause skb_shared_info to spill into next frame. It is a little hard to trigger, as the SKB need to use above 15 skb_shinfo->frags[] as far as I calculate. This does happen in practise for TCP streams when skb_try_coalesce() kicks in. KASAN can be used to detect these wrong memory accesses, I've seen: BUG: KASAN: use-after-free in skb_try_coalesce+0x3cb/0x760 BUG: KASAN: wild-memory-access in skb_release_data+0xe2/0x250 Driver veth also construct a SKB from xdp_frame in this way, but is not affected, as it doesn't reserve/deduct the room (used by xdp_frame) from the SKB headroom. Instead is clears the pointers via xdp_scrub_frame(), and allows SKB to use this area. The fix in this patch is to do like veth and instead allow SKB to (re)use the area occupied by xdp_frame, by clearing via xdp_scrub_frame(). (This does kill the idea of the SKB being able to access (mem) info from this area, but I guess it was a bad idea anyhow, and it was already killed by the veth changes.)

Jesper Dangaard Brouer committed 7 years ago

Commit 676e4a61 parent 8543e431 file · +10 −3Browse files

Unified · Split

kernel/bpf/cpumap.c+10−3
@@ -162,10 +162,14 @@ static void cpu_map_kthread_stop(struct work_struct *work) · 161 unmodified lines
162162 static struct sk_buff *cpu_map_build_skb(struct bpf_cpu_map_entry *rcpu,
163163 struct xdp_frame *xdpf)
164164 {
165+ unsigned int hard_start_headroom;
165166 unsigned int frame_size;
166167 void *pkt_data_start;
167168 struct sk_buff *skb;
168169
170+ /* Part of headroom was reserved to xdpf */
171+ hard_start_headroom = sizeof(struct xdp_frame) + xdpf->headroom;
172+
169173 /* build_skb need to place skb_shared_info after SKB end, and
170174 * also want to know the memory "truesize". Thus, need to
171175 * know the memory frame size backing xdp_buff.
@@ -183,15 +187,15 @@ static struct sk_buff *cpu_map_build_skb(struct bpf_cpu_map_entry *rcpu, · 11 unmodified lines
183187 * is not at a fixed memory location, with mixed length
184188 * packets, which is bad for cache-line hotness.
185189 */
186− frame_size = SKB_DATA_ALIGN(xdpf->len + xdpf->headroom) +
190+ frame_size = SKB_DATA_ALIGN(xdpf->len + hard_start_headroom) +
187191 SKB_DATA_ALIGN(sizeof(struct skb_shared_info));
188192
189− pkt_data_start = xdpf->data - xdpf->headroom;
193+ pkt_data_start = xdpf->data - hard_start_headroom;
190194 skb = build_skb(pkt_data_start, frame_size);
191195 if (!skb)
192196 return NULL;
193197
194− skb_reserve(skb, xdpf->headroom);
198+ skb_reserve(skb, hard_start_headroom);
195199 __skb_put(skb, xdpf->len);
196200 if (xdpf->metasize)
197201 skb_metadata_set(skb, xdpf->metasize);
@@ -205,6 +209,9 @@ static struct sk_buff *cpu_map_build_skb(struct bpf_cpu_map_entry *rcpu, · 7 unmodified lines
205209 * - RX ring dev queue index (skb_record_rx_queue)
206210 */
207211
212+ /* Allow SKB to reuse area used by xdp_frame */
213+ xdp_scrub_frame(xdpf);
214+
208215 return skb;
209216 }
210217