# xsk: fix an integer overflow in xp_create_and_assign_umem()

CVE record · `CVE-2025-21997`

- **Identifiers:** `CVE-2025-21997`
- **State:** Confirmed
- **Severity:** CVSS 5.5 Medium
- **Critical:** No
- **CNA:** Linux
- **Weakness (CWE):** [CWE-190](https://cwe.mitre.org/data/definitions/190.html)
- **Tags:** [Memory corruption](https://agentprime.io/advisories/tag/memory-corruption.md)
- **Technologies:** [Linux kernel](https://agentprime.io/advisories/technology/linux-kernel.md)
- **Published:** 3 Apr 2025
- **Updated:** 11 May 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: Linux) at 3 Apr 2025, 07:19 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it.

## Affected products, as the CNA wrote them

- Vendor: Linux. Product: Linux.
  - affected: `94033cd8e73b8632bab7c8b7bb54caa4f5616db7 to before 205649d642a5b376724f04f3a5b3586815e43d3b` (git)
  - affected: `94033cd8e73b8632bab7c8b7bb54caa4f5616db7 to before b7b4be1fa43294b50b22e812715198629806678a` (git)
  - affected: `94033cd8e73b8632bab7c8b7bb54caa4f5616db7 to before 130290f44bce0eead2b827302109afc3fe189ddd` (git)
  - affected: `94033cd8e73b8632bab7c8b7bb54caa4f5616db7 to before c7670c197b0f1a8726ad5c87bc2bf001a1fc1bbd` (git)
  - affected: `94033cd8e73b8632bab7c8b7bb54caa4f5616db7 to before 559847f56769037e5b2e0474d3dbff985b98083d` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `5.16`
  - unaffected: `before 5.16` (semver)
  - unaffected: `6.1.132 to 6.1.*, inclusive` (semver)
  - unaffected: `6.6.85 to 6.6.*, inclusive` (semver)
  - unaffected: `6.12.21 to 6.12.*, inclusive` (semver)
  - unaffected: `6.13.9 to 6.13.*, inclusive` (semver)
  - unaffected: `6.14 to *, inclusive` (original_commit_for_fix)
  - Other versions: affected

## Not analysed yet

We haven’t published our own analysis of this CVE. If a person reviews it, this page will say what’s affected and what has to be true for it to matter.

## Severity and exploitation

- 5.5 Medium, CVSS 3.1: `CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`, from ADP (CISA-ADP)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0021, the 10th percentile, on 20 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

This record came from the full history of the CVE Program, published 3 Apr 2025. New records show when each source confirmed them.

## Sources

- [CVE List: CVE-2025-21997](https://www.cve.org/CVERecord?id=CVE-2025-21997)
- [NVD: CVE-2025-21997](https://nvd.nist.gov/vuln/detail/CVE-2025-21997)

### References from the CNA

- <https://git.kernel.org/stable/c/205649d642a5b376724f04f3a5b3586815e43d3b>
- <https://git.kernel.org/stable/c/b7b4be1fa43294b50b22e812715198629806678a>
- <https://git.kernel.org/stable/c/130290f44bce0eead2b827302109afc3fe189ddd>
- <https://git.kernel.org/stable/c/c7670c197b0f1a8726ad5c87bc2bf001a1fc1bbd>
- <https://git.kernel.org/stable/c/559847f56769037e5b2e0474d3dbff985b98083d>

Facts on this page come from the CVE List as the CNA published them, with CVSS from the sources named above, CISA KEV and FIRST EPSS. Vendors, products and versions are shown as the CNA wrote them. We don’t reproduce the CVE’s description.

## Check whether this affects you

This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it. Compare the affected versions above with what you run.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), `get_advisory` returns this record and `search_advisories` finds related ones. Setup: <https://agentprime.io/mcp.md>
- As JSON: <https://api.agentprime.io/v1/advisories/CVE-2025-21997>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

The web page: <https://agentprime.io/advisories/CVE-2025-21997/>. Everything for agents: <https://agentprime.io/llms.txt>.
