Vulnerability Details : CVE-2025-22005
In the Linux kernel, the following vulnerability has been resolved:
ipv6: Fix memleak of nhc_pcpu_rth_output in fib_check_nh_v6_gw().
fib_check_nh_v6_gw() expects that fib6_nh_init() cleans up everything
when it fails.
Commit 7dd73168e273 ("ipv6: Always allocate pcpu memory in a fib6_nh")
moved fib_nh_common_init() before alloc_percpu_gfp() within fib6_nh_init()
but forgot to add cleanup for fib6_nh->nh_common.nhc_pcpu_rth_output in
case it fails to allocate fib6_nh->rt6i_pcpu, resulting in memleak.
Let's call fib_nh_common_release() and clear nhc_pcpu_rth_output in the
error path.
Note that we can remove the fib6_nh_release() call in nh_create_ipv6()
later in net-next.git.
Products affected by CVE-2025-22005
- cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
- cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
- cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
- cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
- cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
- cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
- cpe:2.3:o:linux:linux_kernel:6.14:rc1:*:*:*:*:*:*
- cpe:2.3:o:linux:linux_kernel:6.14:rc2:*:*:*:*:*:*
- cpe:2.3:o:linux:linux_kernel:6.14:rc3:*:*:*:*:*:*
- cpe:2.3:o:linux:linux_kernel:6.14:rc4:*:*:*:*:*:*
- cpe:2.3:o:linux:linux_kernel:6.14:rc5:*:*:*:*:*:*
- cpe:2.3:o:linux:linux_kernel:6.14:rc6:*:*:*:*:*:*
- cpe:2.3:o:linux:linux_kernel:6.14:rc7:*:*:*:*:*:*
Exploit prediction scoring system (EPSS) score for CVE-2025-22005
0.02%
Probability of exploitation activity in the next 30 days
EPSS Score History
~ 3 %
Percentile, the proportion of vulnerabilities that are scored at or less
CVSS scores for CVE-2025-22005
Base Score | Base Severity | CVSS Vector | Exploitability Score | Impact Score | Score Source | First Seen |
---|---|---|---|---|---|---|
5.5
|
MEDIUM | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
1.8
|
3.6
|
NIST | 2025-04-10 |
5.5
|
MEDIUM | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
N/A
|
N/A
|
RedHat-CVE-2025-22005 | 2025-04-04 |
CWE ids for CVE-2025-22005
-
The product does not sufficiently track and release allocated memory after it has been used, making the memory unavailable for reallocation and reuse.Assigned by: nvd@nist.gov (Primary)
References for CVE-2025-22005
-
https://git.kernel.org/stable/c/1bd12dfc058e1e68759d313d7727d68dbc1b8964
Patch
-
https://git.kernel.org/stable/c/16267a5036173d0173377545b4b6021b081d0933
Patch
-
https://git.kernel.org/stable/c/596a883c4ce2d2e9c175f25b98fed3a1f33fea38
Patch
-
https://git.kernel.org/stable/c/d3d5b4b5ae263c3225db363ba08b937e2e2b0380
Patch
-
https://git.kernel.org/stable/c/119dcafe36795a15ae53351cbbd6177aaf94ffef
Patch
-
https://git.kernel.org/stable/c/29d91820184d5cbc70f3246d4911d96eaeb930d6
Patch
-
https://git.kernel.org/stable/c/77c41cdbe6bce476e08d3251c0d501feaf10a9f3
Patch
-
https://git.kernel.org/stable/c/9740890ee20e01f99ff1dde84c63dcf089fabb98
Patch
Jump to