https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Mon, 05 Oct 2026 09:01:11 +0000 https://cve.radiocsirt.org/vuln/cve-2022-22209 <p><strong>Affected:</strong> Juniper Networks Junos OS</p> <p>A Missing Release of Memory after Effective Lifetime vulnerability in the kernel of Juniper Networks Junos OS allows an unauthenticated network based attacker to cause a Denial of Service (DoS). On all Junos platforms, the Kernel Routing Table (KRT) queue can get stuck due to a memory leak triggered by interface flaps or route churn leading to RIB and PFEs getting out of sync. The memory leak causes RTNEXTHOP/route and next-hop memory pressure issue and the KRT queue will eventually get stuck with the error- &#39;ENOMEM -- Cannot allocate memory&#39;. The out-of-sync state between RIB and FIB can be seen with the &#34;show route&#34; and &#34;show route forwarding-table&#34; command. This issue will lead to failures for adding new routes. The KRT queue status can be checked using the CLI command &#34;show krt queue&#34;: user@host &gt; show krt state High-priority add queue: 1 queued ADD nhtype Router index 0 (31212) error &#39;ENOMEM -- Cannot allocate memory&#39; kqp &#39;0x8ad5e40&#39; The following messages will be observed in /var/log/messages, which indicate high memory for routes/nexthops: host rpd[16279]: RPD_RT_HWM_NOTICE: New RIB highwatermark for routes: 266 [2022-03-04 05:06:07] host rpd[16279]: RPD_KRT_Q_RETRIES: nexthop ADD: Cannot allocate memory host rpd[16279]: RPD_KRT_Q_RETRIES: nexthop ADD: Cannot allocate memory host kernel: rts_veto_net_delayed_unref_limit: Route/nexthop memory is severe pressure. User Application to perform recovery actions. O p 8 err 12, rtsm_id 0:-1, msg type 10, veto simulation: 0. h…</p> <p><strong>Affected:</strong> Juniper Networks Junos OS</p> <p>A Missing Release of Memory after Effective Lifetime vulnerability in the kernel of Juniper Networks Junos OS allows an unauthenticated network based attacker to cause a Denial of Service (DoS). On all Junos platforms, the Kernel Routing Table (KRT) queue can get stuck due to a memory leak triggered by interface flaps or route churn leading to RIB and PFEs getting out of sync. The memory leak causes RTNEXTHOP/route and next-hop memory pressure issue and the KRT queue will eventually get stuck with the error- &#39;ENOMEM -- Cannot allocate memory&#39;. The out-of-sync state between RIB and FIB can be seen with the &#34;show route&#34; and &#34;show route forwarding-table&#34; command. This issue will lead to failures for adding new routes. The KRT queue status can be checked using the CLI command &#34;show krt queue&#34;: user@host &gt; show krt state High-priority add queue: 1 queued ADD nhtype Router index 0 (31212) error &#39;ENOMEM -- Cannot allocate memory&#39; kqp &#39;0x8ad5e40&#39; The following messages will be observed in /var/log/messages, which indicate high memory for routes/nexthops: host rpd[16279]: RPD_RT_HWM_NOTICE: New RIB highwatermark for routes: 266 [2022-03-04 05:06:07] host rpd[16279]: RPD_KRT_Q_RETRIES: nexthop ADD: Cannot allocate memory host rpd[16279]: RPD_KRT_Q_RETRIES: nexthop ADD: Cannot allocate memory host kernel: rts_veto_net_delayed_unref_limit: Route/nexthop memory is severe pressure. User Application to perform recovery actions. O p 8 err 12, rtsm_id 0:-1, msg type 10, veto simulation: 0. h…</p> https://cve.radiocsirt.org/vuln/cve-2022-22209