CVE-2026-43092
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…
Does this matter?
Lower severity and a low EPSS score (0.12%). Track it; it rarely justifies an emergency change on its own.
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).
- CVSS 3.1
- 5.5 MEDIUMCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
- EPSS
- 0.12% probability · 2th percentile
- CISA KEV
- Not listed
- Affected
- linux/linux kernel
- Source
- 416baaa9-dc9f-4396-8d5f-8c081fb06d67
References
- https://git.kernel.org/stable/c/25e1e91a8da819924df0b16e3812d7b24c8ce133Patch
- https://git.kernel.org/stable/c/36ee60b569ba0dfb6f961333b90d19ab5b323fa9Patch
- https://git.kernel.org/stable/c/a55793e5a97d4e39bdb380873a9780fe0010bff6Patch
- https://git.kernel.org/stable/c/b2f4daa6422fd6cc0cec969794dab4a88ea4cea1Patch
- https://git.kernel.org/stable/c/f669d60db11dbabb96279f2b20f9d1cba43cddb2Patch
Source: NVD record, EPSS from FIRST.org, KEV from CISA. Refreshed daily.