<?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://vulnerability.circl.lu</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>Thu, 01 Oct 2026 22:38:00 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-72421 — ipv4: fib: Don't ignore error route in local/main tables.</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-72421</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;ipv4: fib: Don&amp;#39;t ignore error route in local/main tables.&lt;/p&gt;
&lt;p&gt;When CONFIG_IP_MULTIPLE_TABLES is enabled but no rule is added,
fib_lookup() performs route lookup directly on two tables.&lt;/p&gt;
&lt;p&gt;Since the first lookup does not properly bail out, the result
of an error route in the merged local/main table could be
overwritten by another route in the default table:&lt;/p&gt;
&lt;p&gt;# unshare -n
  # ip link set lo up
  # ip route add 192.168.0.0/24 dev lo table 253
  # ip route add unreachable 192.168.0.0/24
  # ip route get 192.168.0.1
  192.168.0.1 dev lo table default uid 0
      cache &amp;lt;local&amp;gt;&lt;/p&gt;
&lt;p&gt;Once a random rule is added, the error route is respected:&lt;/p&gt;
&lt;p&gt;# ip rule add table 0
  # ip rule del table 0
  # ip route get 192.168.0.1
  RTNETLINK answers: No route to host&lt;/p&gt;
&lt;p&gt;Let&amp;#39;s fix the inconsistent behaviour.&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;ipv4: fib: Don&amp;#39;t ignore error route in local/main tables.&lt;/p&gt;
&lt;p&gt;When CONFIG_IP_MULTIPLE_TABLES is enabled but no rule is added,
fib_lookup() performs route lookup directly on two tables.&lt;/p&gt;
&lt;p&gt;Since the first lookup does not properly bail out, the result
of an error route in the merged local/main table could be
overwritten by another route in the default table:&lt;/p&gt;
&lt;p&gt;# unshare -n
  # ip link set lo up
  # ip route add 192.168.0.0/24 dev lo table 253
  # ip route add unreachable 192.168.0.0/24
  # ip route get 192.168.0.1
  192.168.0.1 dev lo table default uid 0
      cache &amp;lt;local&amp;gt;&lt;/p&gt;
&lt;p&gt;Once a random rule is added, the error route is respected:&lt;/p&gt;
&lt;p&gt;# ip rule add table 0
  # ip rule del table 0
  # ip route get 192.168.0.1
  RTNETLINK answers: No route to host&lt;/p&gt;
&lt;p&gt;Let&amp;#39;s fix the inconsistent behaviour.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-72421</guid>
    </item>
  </channel>
</rss>
