Description
In the Linux kernel, the following vulnerability has been resolved: xsk: validate MTU against usable frame size on bind AF_XDP bind currently accepts zero-copy pool configurations without verifying that the device MTU fits into the usable frame space provided by the UMEM chunk. This becomes a problem since we started to respect tailroom which is subtracted from chunk_size (among with headroom). 2k chunk size might not provide enough space for standard 1500 MTU, so let us catch such settings at bind time. Furthermore, validate whether underlying HW will be able to satisfy configured MTU wrt XSK's frame size multiplied by supported Rx buffer chain length (that is exposed via net_device::xdp_zc_max_segs).
Affected products
linux: linux kernel
References5
- git.kernel.org/stable/c/25e1e91a8da819924df0b16e3812d7b24c8ce133 Patch
- git.kernel.org/stable/c/36ee60b569ba0dfb6f961333b90d19ab5b323fa9 Patch
- git.kernel.org/stable/c/a55793e5a97d4e39bdb380873a9780fe0010bff6 Patch
- git.kernel.org/stable/c/b2f4daa6422fd6cc0cec969794dab4a88ea4cea1 Patch
- git.kernel.org/stable/c/f669d60db11dbabb96279f2b20f9d1cba43cddb2 Patch
Metrics
- CVSS 3.1
-
5.5
MEDIUM
Score source: NVD
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H - EPSS — exploit probability
- 0% percentile: 2 · as of 13 November 2026
Could this be exploited in your environment?
A patch closes the known hole. A penetration test shows what an attacker can still reach — with proof.