CVE-2025-38588: Linux kernel · ipv6: prevent infinite loop in rt6_nlmsg_size()
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in e1b7932af47f92432be8303d2439d1bf77b0be23 : update Linux kernel when convenient.
Data as of 5 Nov 2026, 23:23 UTC
Rated by Threat Radar · No CVSS score from NVD or the CNA
Thin evidence
One scorer or none- EPSS
- 0.1% chance of exploitation in 30 days – higher than 6% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- CISA SSVC
- Exploitation
- No evidence of active exploitation and no public proof of concept
- Automatable
- Attackers cannot reliably automate steps 1–4 of the kill chain
- Technical impact
- Limited control over the software or limited information exposure
CISA SSVC assessment, 2026-11-05.
- Patch
- Available – fixed in e1b7932af47f92432be8303d2439d1bf77b0be23, cd8d8bbd9ced4cc5d06d858f67d4aa87745e8f38, 54e6fe9dd3b0e7c481c2228782c9494d653546da +7
Exploitation evidence
Disclosed: evidence found.
CVE published 19 Aug 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
Description
In the Linux kernel, the following vulnerability has been resolved: ipv6: prevent infinite loop in rt6_nlmsg_size() While testing prior patch, I was able to trigger an infinite loop in rt6_nlmsg_size() in the following place: list_for_each_entry_rcu(sibling, &f6i->fib6_siblings, fib6_siblings) { rt6_nh_nlmsg_size(sibling->fib6_nh, &nexthop_len); } This is because fib6_del_route() and fib6_add_rt2node() uses list_del_rcu(), which can confuse rcu readers, because they might no longer see the head of the list. Restart the loop if f6i->fib6_nsiblings is zero.
References
- git.kernel.org/stable/c/6d345136c9b875f065d226908a29c25cdf9343f8 (opens in a new tab)
- git.kernel.org/stable/c/e1b7932af47f92432be8303d2439d1bf77b0be23 (opens in a new tab)
- git.kernel.org/stable/c/cd8d8bbd9ced4cc5d06d858f67d4aa87745e8f38 (opens in a new tab)
- git.kernel.org/stable/c/3c13db3e47e170bab19e574404e7b6be45ea873d (opens in a new tab)
- git.kernel.org/stable/c/46aeb66e9e54ed0d56c18615e1c3dbd502b327ab (opens in a new tab)
- git.kernel.org/stable/c/54e6fe9dd3b0e7c481c2228782c9494d653546da (opens in a new tab)
- lists.debian.org/debian-lts-announce/2025/10/msg00008.html (opens in a new tab)