CVE-2026-43093

xsk: tighten UMEM headroom validation to account for tailroom and min frame

HIGH
7.8
CVSS Score
Published: May 6, 2026 at 07:40 AM UTC
Updated: October 19, 2026 at 08:18 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.8
Exploit prediction
EPSS 0.1%
SSVC
No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: xsk: tighten UMEM headroom validation to account for tailroom and min frame The current headroom validation in xdp_umem_reg() could leave us with insufficient space dedicated to even receive minimum-sized ethernet frame. Furthermore if multi-buffer would come to play then skb_shared_info stored at the end of XSK frame would be corrupted. HW typically works with 128-aligned sizes so let us provide this value as bare minimum. Multi-buffer setting is known later in the configuration process so besides accounting for 128 bytes, let us also take care of tailroom space upfront.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

4.19.118 ≤ v < 4.205.4.35 ≤ v < 5.55.6.7 ≤ v < 5.75.7.1 ≤ v < 6.6.1366.13 ≤ v < 6.18.246.19 ≤ v < 6.19.146.7 ≤ v < 6.12.8325c9cdef57488578da21d99eb614b97ffcf6e59f4.19.1185.4.355.6.75.75.7 rc25.7 rc35.7 rc45.7 rc55.7 rc65.7 rc77.07.0 rc17.0 rc27.0 rc37.0 rc47.0 rc57.0 rc67.0 rc798d3c852e63b49129515dd18c875999efaf8530a99e3a236dd43d06c65af0a2ef9cb44306aef6e02ad8fb61c184fe0f8d1e0b5b954d010fb9f94a6ee
Vendor states this is fixed in 0ec4d3f6e6934deb843b561ae048cd17218e5ad1 (fixed)
Vendor states this is fixed in 1a6051cd7e3e4c54ff3854a43b638b9292af5e67 (fixed)
Vendor states this is fixed in 5f123bc278bf4e3283d8606321bebbfd299f4384 (fixed)
Vendor states this is fixed in 6523bc1b40e69301f24c14338b762af4739d6d39 (fixed)
Vendor states this is fixed in 8769708add9eadeea8041a9761771bb715a87104 (fixed)
Vendor states this is fixed in 9ea6ba4f3195dcba6e8b3e7b2e748593b7cafb12 (fixed)
Vendor states this is fixed in a03975beb9f6af0d8ac051e30b2abeabe618414f (fixed)
Vendor states this is fixed in a315e022a72d95ef5f1d4e58e903cb492b0ad931 (fixed)
Affected range stops below 4.20, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 5.10.258 (unaffected)
Vendor states this is fixed in 5.15.209 (unaffected)
Affected range stops below 5.5, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 5.7 (unaffected)
Vendor states this is fixed in 6.1.175 (unaffected)
Vendor states this is fixed in 6.12.83 (unaffected)
Vendor states this is fixed in 6.18.24 (unaffected)
Vendor states this is fixed in 6.19.14 (unaffected)
Vendor states this is fixed in 6.6.136 (unaffected)
Vendor states this is fixed in 7.0 (unaffected)

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.8HIGHLinux
Vector?

Quick Info

StatusMODIFIED
CWE
NVD-CWE-noinfoCWE-787

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card