net: mvpp2: limit XDP frame size to the RX buffer
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 07dd0a7aae7f72af7cec18909581c2bb570edddc · < 9545cc5ef18ca22d031f2f47c157192460652359| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
net: mvpp2: limit XDP frame size to the RX buffer
mvpp2 has short and long BM pools, and short pool buffers can be smaller than PAGE_SIZE. The XDP path nevertheless initializes every xdp_buff with PAGE_SIZE as frame size.
XDP helpers use frame_sz to validate tail growth and to derive the hard end of the data area. Advertising PAGE_SIZE for short buffers can let bpf_xdp_adjust_tail() grow a packet past the real allocation, corrupting memory or later tripping skb tailroom checks.
Initialize the XDP buffer with bm_pool->frag_size so XDP tailroom matches the actual buffer backing the packet.
From the CVE record · Linux
The Linux kernel’s mvpp2 driver reports an XDP frame size larger than the actual allocation for short buffer pools. When bpf_xdp_adjust_tail() grows a packet using that incorrect size, it can corrupt memory or trigger later tailroom checks. The input does not specify an attack path, authentication requirements, or user interaction.
Engineers running Linux kernels with the mvpp2 driver and XDP should check their affected versions against the vendor advisory; no version range was provided.