<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Tue, 06 Oct 2026 14:39:36 +0000</lastBuildDate>
    <item>
      <title>CVE-2021-47363 — nexthop: Fix division by zero while replacing a resilient group</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2021-47363</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;nexthop: Fix division by zero while replacing a resilient group&lt;/p&gt;
&lt;p&gt;The resilient nexthop group torture tests in fib_nexthop.sh exposed a
possible division by zero while replacing a resilient group [1]. The
division by zero occurs when the data path sees a resilient nexthop
group with zero buckets.&lt;/p&gt;
&lt;p&gt;The tests replace a resilient nexthop group in a loop while traffic is
forwarded through it. The tests do not specify the number of buckets
while performing the replacement, resulting in the kernel allocating a
stub resilient table (i.e, &amp;#39;struct nh_res_table&amp;#39;) with zero buckets.&lt;/p&gt;
&lt;p&gt;This table should never be visible to the data path, but the old nexthop
group (i.e., &amp;#39;oldg&amp;#39;) might still be used by the data path when the stub
table is assigned to it.&lt;/p&gt;
&lt;p&gt;Fix this by only assigning the stub table to the old nexthop group after
making sure the group is no longer used by the data path.&lt;/p&gt;
&lt;p&gt;Tested with fib_nexthops.sh:&lt;/p&gt;
&lt;p&gt;Tests passed: 222
Tests failed:   0&lt;/p&gt;
&lt;p&gt;[1]
 divide error: 0000 [#1] PREEMPT SMP KASAN
 CPU: 0 PID: 1850 Comm: ping Not tainted 5.14.0-custom-10271-ga86eb53057fe #1107
 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.14.0-4.fc34 04/01/2014
 RIP: 0010:nexthop_select_path+0x2d2/0x1a80
[...]
 Call Trace:
  fib_select_multipath+0x79b/0x1530
  fib_select_path+0x8fb/0x1c10
  ip_route_output_key_hash_rcu+0x1198/0x2da0
  ip_route_output_key_hash+0x190/0x340
  ip_route_output_flow+0x21/0x120
  raw_sendmsg+0x91d…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;nexthop: Fix division by zero while replacing a resilient group&lt;/p&gt;
&lt;p&gt;The resilient nexthop group torture tests in fib_nexthop.sh exposed a
possible division by zero while replacing a resilient group [1]. The
division by zero occurs when the data path sees a resilient nexthop
group with zero buckets.&lt;/p&gt;
&lt;p&gt;The tests replace a resilient nexthop group in a loop while traffic is
forwarded through it. The tests do not specify the number of buckets
while performing the replacement, resulting in the kernel allocating a
stub resilient table (i.e, &amp;#39;struct nh_res_table&amp;#39;) with zero buckets.&lt;/p&gt;
&lt;p&gt;This table should never be visible to the data path, but the old nexthop
group (i.e., &amp;#39;oldg&amp;#39;) might still be used by the data path when the stub
table is assigned to it.&lt;/p&gt;
&lt;p&gt;Fix this by only assigning the stub table to the old nexthop group after
making sure the group is no longer used by the data path.&lt;/p&gt;
&lt;p&gt;Tested with fib_nexthops.sh:&lt;/p&gt;
&lt;p&gt;Tests passed: 222
Tests failed:   0&lt;/p&gt;
&lt;p&gt;[1]
 divide error: 0000 [#1] PREEMPT SMP KASAN
 CPU: 0 PID: 1850 Comm: ping Not tainted 5.14.0-custom-10271-ga86eb53057fe #1107
 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.14.0-4.fc34 04/01/2014
 RIP: 0010:nexthop_select_path+0x2d2/0x1a80
[...]
 Call Trace:
  fib_select_multipath+0x79b/0x1530
  fib_select_path+0x8fb/0x1c10
  ip_route_output_key_hash_rcu+0x1198/0x2da0
  ip_route_output_key_hash+0x190/0x340
  ip_route_output_flow+0x21/0x120
  raw_sendmsg+0x91d…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2021-47363</guid>
    </item>
  </channel>
</rss>
