# ipv6: Fix memleak of nhc_pcpu_rth_output in fib_check_nh_v6_gw().

CVE record · `CVE-2025-22005`

- **Identifiers:** `CVE-2025-22005`
- **State:** Confirmed
- **Severity:** CVSS 5.5 Medium
- **Critical:** No
- **CNA:** Linux
- **Weakness (CWE):** [CWE-401](https://cwe.mitre.org/data/definitions/401.html)
- **Tags:** [Denial of service](https://agentprime.io/advisories/tag/dos.md)
- **Technologies:** [Linux kernel](https://agentprime.io/advisories/technology/linux-kernel.md)
- **Published:** 3 Apr 2025
- **Updated:** 10 Nov 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: `7dd73168e273938b9e9bb42ca51b0c27d807992b to before 16267a5036173d0173377545b4b6021b081d0933` (git)
  - affected: `7dd73168e273938b9e9bb42ca51b0c27d807992b to before 1bd12dfc058e1e68759d313d7727d68dbc1b8964` (git)
  - affected: `7dd73168e273938b9e9bb42ca51b0c27d807992b to before 596a883c4ce2d2e9c175f25b98fed3a1f33fea38` (git)
  - affected: `7dd73168e273938b9e9bb42ca51b0c27d807992b to before 77c41cdbe6bce476e08d3251c0d501feaf10a9f3` (git)
  - affected: `7dd73168e273938b9e9bb42ca51b0c27d807992b to before 119dcafe36795a15ae53351cbbd6177aaf94ffef` (git)
  - affected: `7dd73168e273938b9e9bb42ca51b0c27d807992b to before 29d91820184d5cbc70f3246d4911d96eaeb930d6` (git)
  - affected: `7dd73168e273938b9e9bb42ca51b0c27d807992b to before d3d5b4b5ae263c3225db363ba08b937e2e2b0380` (git)
  - affected: `7dd73168e273938b9e9bb42ca51b0c27d807992b to before 9740890ee20e01f99ff1dde84c63dcf089fabb98` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `5.3`
  - unaffected: `before 5.3` (semver)
  - unaffected: `5.4.292 to 5.4.*, inclusive` (semver)
  - unaffected: `5.10.236 to 5.10.*, inclusive` (semver)
  - unaffected: `5.15.180 to 5.15.*, inclusive` (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.0022, the 12th percentile, on 17 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 3 Apr 2025, 07:19 UTC: [Confirmed by the CVE List](https://www.cve.org/CVERecord?id=CVE-2025-22005)
- 3 Apr 2025, 08:15 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2025-22005)

## Sources

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

### References from the CNA

- <https://git.kernel.org/stable/c/16267a5036173d0173377545b4b6021b081d0933>
- <https://git.kernel.org/stable/c/1bd12dfc058e1e68759d313d7727d68dbc1b8964>
- <https://git.kernel.org/stable/c/596a883c4ce2d2e9c175f25b98fed3a1f33fea38>
- <https://git.kernel.org/stable/c/77c41cdbe6bce476e08d3251c0d501feaf10a9f3>
- <https://git.kernel.org/stable/c/119dcafe36795a15ae53351cbbd6177aaf94ffef>
- <https://git.kernel.org/stable/c/29d91820184d5cbc70f3246d4911d96eaeb930d6>
- <https://git.kernel.org/stable/c/d3d5b4b5ae263c3225db363ba08b937e2e2b0380>
- <https://git.kernel.org/stable/c/9740890ee20e01f99ff1dde84c63dcf089fabb98>

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-22005>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

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