<?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>Fri, 09 Oct 2026 21:46:57 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-98303</title>
      <link>https://vulnerability.circl.lu/vuln/bell-cve-2026-98303</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/bell-cve-2026-98303</guid>
    </item>
    <item>
      <title>fkie_cve-2026-98303</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2026-98303</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ipv4: icmp: reject RTN_UNREACHABLE input routes in icmp_route_lookup&lt;/p&gt;
&lt;p&gt;When the forward output route cannot be used in icmp_route_lookup(),
it enters the &amp;#34;reverse path&amp;#34; and calls ip_route_input() on fl4_dec.daddr,
the original packet&amp;#39;s source address.&lt;/p&gt;
&lt;p&gt;ip_route_input() only returns an error for truly invalid packets. For
unreachable addresses it will succeed and return an input route whose
dst.output is set to ip_rt_bug(). The existing check only rejects
RTN_LOCAL routes, so the RTN_UNREACHABLE route types can still be returned
and later used for output, syzkaller triggering a WARN_ON_ONCE()
in ip_rt_bug() as bellow:&lt;/p&gt;
&lt;p&gt;------------[ cut here ]------------
 WARNING: net/ipv4/route.c:1273 at ip_rt_bug+0x14/0x20
 RIP: 0010:ip_rt_bug+0x14/0x20
 Call Trace:
  ip_push_pending_frames+0xfa/0x100
  __icmp_send+0x905/0xf10
  ip_options_compile+0xc0/0xd0
  ip_rcv_finish_core+0x321/0xae0
  ip_rcv+0x1de/0x260
  __netif_receive_skb_one_core+0x11a/0x130
  netif_receive_skb+0x7b/0x260
  tun_get_user+0x11bf/0x1c10
 ------------[ cut here ]------------&lt;/p&gt;
&lt;p&gt;Reject input route that is RTN_UNREACHABLE to fix it. The net warning
is only printed for RTN_LOCAL, as RTN_UNREACHABLE is not the result of
a race condition.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ipv4: icmp: reject RTN_UNREACHABLE input routes in icmp_route_lookup&lt;/p&gt;
&lt;p&gt;When the forward output route cannot be used in icmp_route_lookup(),
it enters the &amp;#34;reverse path&amp;#34; and calls ip_route_input() on fl4_dec.daddr,
the original packet&amp;#39;s source address.&lt;/p&gt;
&lt;p&gt;ip_route_input() only returns an error for truly invalid packets. For
unreachable addresses it will succeed and return an input route whose
dst.output is set to ip_rt_bug(). The existing check only rejects
RTN_LOCAL routes, so the RTN_UNREACHABLE route types can still be returned
and later used for output, syzkaller triggering a WARN_ON_ONCE()
in ip_rt_bug() as bellow:&lt;/p&gt;
&lt;p&gt;------------[ cut here ]------------
 WARNING: net/ipv4/route.c:1273 at ip_rt_bug+0x14/0x20
 RIP: 0010:ip_rt_bug+0x14/0x20
 Call Trace:
  ip_push_pending_frames+0xfa/0x100
  __icmp_send+0x905/0xf10
  ip_options_compile+0xc0/0xd0
  ip_rcv_finish_core+0x321/0xae0
  ip_rcv+0x1de/0x260
  __netif_receive_skb_one_core+0x11a/0x130
  netif_receive_skb+0x7b/0x260
  tun_get_user+0x11bf/0x1c10
 ------------[ cut here ]------------&lt;/p&gt;
&lt;p&gt;Reject input route that is RTN_UNREACHABLE to fix it. The net warning
is only printed for RTN_LOCAL, as RTN_UNREACHABLE is not the result of
a race condition.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/fkie_cve-2026-98303</guid>
    </item>
    <item>
      <title>GHSA-hw8j-26f4-2863</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-hw8j-26f4-2863</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ipv4: icmp: reject RTN_UNREACHABLE input routes in icmp_route_lookup&lt;/p&gt;
&lt;p&gt;When the forward output route cannot be used in icmp_route_lookup(),
it enters the &amp;#34;reverse path&amp;#34; and calls ip_route_input() on fl4_dec.daddr,
the original packet&amp;#39;s source address.&lt;/p&gt;
&lt;p&gt;ip_route_input() only returns an error for truly invalid packets. For
unreachable addresses it will succeed and return an input route whose
dst.output is set to ip_rt_bug(). The existing check only rejects
RTN_LOCAL routes, so the RTN_UNREACHABLE route types can still be returned
and later used for output, syzkaller triggering a WARN_ON_ONCE()
in ip_rt_bug() as bellow:&lt;/p&gt;
&lt;p&gt;------------[ cut here ]------------
 WARNING: net/ipv4/route.c:1273 at ip_rt_bug+0x14/0x20
 RIP: 0010:ip_rt_bug+0x14/0x20
 Call Trace:
  ip_push_pending_frames+0xfa/0x100
  __icmp_send+0x905/0xf10
  ip_options_compile+0xc0/0xd0
  ip_rcv_finish_core+0x321/0xae0
  ip_rcv+0x1de/0x260
  __netif_receive_skb_one_core+0x11a/0x130
  netif_receive_skb+0x7b/0x260
  tun_get_user+0x11bf/0x1c10
 ------------[ cut here ]------------&lt;/p&gt;
&lt;p&gt;Reject input route that is RTN_UNREACHABLE to fix it. The net warning
is only printed for RTN_LOCAL, as RTN_UNREACHABLE is not the result of
a race condition.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ipv4: icmp: reject RTN_UNREACHABLE input routes in icmp_route_lookup&lt;/p&gt;
&lt;p&gt;When the forward output route cannot be used in icmp_route_lookup(),
it enters the &amp;#34;reverse path&amp;#34; and calls ip_route_input() on fl4_dec.daddr,
the original packet&amp;#39;s source address.&lt;/p&gt;
&lt;p&gt;ip_route_input() only returns an error for truly invalid packets. For
unreachable addresses it will succeed and return an input route whose
dst.output is set to ip_rt_bug(). The existing check only rejects
RTN_LOCAL routes, so the RTN_UNREACHABLE route types can still be returned
and later used for output, syzkaller triggering a WARN_ON_ONCE()
in ip_rt_bug() as bellow:&lt;/p&gt;
&lt;p&gt;------------[ cut here ]------------
 WARNING: net/ipv4/route.c:1273 at ip_rt_bug+0x14/0x20
 RIP: 0010:ip_rt_bug+0x14/0x20
 Call Trace:
  ip_push_pending_frames+0xfa/0x100
  __icmp_send+0x905/0xf10
  ip_options_compile+0xc0/0xd0
  ip_rcv_finish_core+0x321/0xae0
  ip_rcv+0x1de/0x260
  __netif_receive_skb_one_core+0x11a/0x130
  netif_receive_skb+0x7b/0x260
  tun_get_user+0x11bf/0x1c10
 ------------[ cut here ]------------&lt;/p&gt;
&lt;p&gt;Reject input route that is RTN_UNREACHABLE to fix it. The net warning
is only printed for RTN_LOCAL, as RTN_UNREACHABLE is not the result of
a race condition.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-hw8j-26f4-2863</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-98303 — ipv4: icmp: reject RTN_UNREACHABLE input routes in icmp_route_lookup</title>
      <link>https://vulnerability.circl.lu/vuln/msrc_cve-2026-98303</link>
      <description>msrc_CVE-2026-98303</description>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/msrc_cve-2026-98303</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-98303</title>
      <link>https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-98303</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 247 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: ipv4: icmp: reject RTN_UNREACHABLE input routes in icmp_route_lookup When the forward output route cannot be used in icmp_route_lookup(), it enters the &amp;#34;reverse path&amp;#34; and calls ip_route_input() on fl4_dec.daddr, the original packet&amp;#39;s source address. ip_route_input() only returns an error for truly invalid packets. For unreachable addresses it will succeed and return an input route whose dst.output is set to ip_rt_bug(). The existing check only rejects RTN_LOCAL routes, so the RTN_UNREACHABLE route types can still be returned and later used for output, syzkaller triggering a WARN_ON_ONCE() in ip_rt_bug() as bellow:  ------------[ cut here ]------------  WARNING: net/ipv4/route.c:1273 at ip_rt_bug+0x14/0x20  RIP: 0010:ip_rt_bug+0x14/0x20  Call Trace:   ip_push_pending_frames+0xfa/0x100   __icmp_send+0x905/0xf10   ip_options_compile+0xc0/0xd0   ip_rcv_finish_core+0x321/0xae0   ip_rcv+0x1de/0x260   __netif_receive_skb_one_core+0x11a/0x130   netif_receive_skb+0x7b/0x260   tun_get_user+0x11bf/0x1c10  ------------[ cut here ]------------ Reject input route that is RTN_UNREACHABLE to fix it. The net warning is only printed for RTN_LOCAL, as RTN_UNREACHABLE is not the result of a race condition.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 247 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: ipv4: icmp: reject RTN_UNREACHABLE input routes in icmp_route_lookup When the forward output route cannot be used in icmp_route_lookup(), it enters the &amp;#34;reverse path&amp;#34; and calls ip_route_input() on fl4_dec.daddr, the original packet&amp;#39;s source address. ip_route_input() only returns an error for truly invalid packets. For unreachable addresses it will succeed and return an input route whose dst.output is set to ip_rt_bug(). The existing check only rejects RTN_LOCAL routes, so the RTN_UNREACHABLE route types can still be returned and later used for output, syzkaller triggering a WARN_ON_ONCE() in ip_rt_bug() as bellow:  ------------[ cut here ]------------  WARNING: net/ipv4/route.c:1273 at ip_rt_bug+0x14/0x20  RIP: 0010:ip_rt_bug+0x14/0x20  Call Trace:   ip_push_pending_frames+0xfa/0x100   __icmp_send+0x905/0xf10   ip_options_compile+0xc0/0xd0   ip_rcv_finish_core+0x321/0xae0   ip_rcv+0x1de/0x260   __netif_receive_skb_one_core+0x11a/0x130   netif_receive_skb+0x7b/0x260   tun_get_user+0x11bf/0x1c10  ------------[ cut here ]------------ Reject input route that is RTN_UNREACHABLE to fix it. The net warning is only printed for RTN_LOCAL, as RTN_UNREACHABLE is not the result of a race condition.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-98303</guid>
    </item>
  </channel>
</rss>
