xdp: reject clones that overrun skb_shared_info tailroom
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ e624d4ed4aa8cc3c69d1359b0aaea539203ed266 · < f463b6f4957c9c3fd1c75f8d3e5af4879fa609c0| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
xdp: reject clones that overrun skb_shared_info tailroom
xdpf_clone() clones broadcast copies into a single page and sets frame_sz to PAGE_SIZE. __xdp_build_skb_from_frame() later treats that page like a normal XDP frame and expects the usual skb_shared_info tailroom at the end of the buffer.
The current check only rejects frames whose linear xdp_frame header, headroom, and packet data exceed PAGE_SIZE. A source frame backed by a larger allocation can still satisfy that check while extending into the clone's required shared-info area. When such a clone is converted back into an skb, build_skb_around() places skb_shared_info over live packet bytes and later writes can corrupt XDP return metadata.
Reject clones unless their linear area fits inside SKB_WITH_OVERHEAD(PAGE_SIZE), matching the tailroom requirement already enforced by the XDP-to-skb conversion path.
From the CVE record · Linux
The Linux kernel’s XDP clone size check can allow a broadcast clone to overlap space reserved for skb_shared_info. When that clone is converted back into an skb, later writes can corrupt XDP return metadata. The input does not specify attacker access requirements or whether user interaction is needed.
Engineers running the Linux kernel should check whether their kernel includes the affected XDP clone handling; affected versions are not specified.