<?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://db.gcve.eu</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>Sat, 17 Oct 2026 18:36:25 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-98278</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-98278</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;net: remove WARN_ON_ONCE() from the dev_fill_forward_path() loop check&lt;/p&gt;
&lt;p&gt;ipip_fill_forward_path() and ip6_tnl_fill_forward_path() look up the
route to the tunnel&amp;#39;s remote endpoint and set ctx-&amp;gt;dev to its device,
which is the tunnel itself when that route resolves back to the tunnel.
dev_fill_forward_path() then makes no progress and trips
WARN_ON_ONCE(last_dev == ctx-&amp;gt;dev) as soon as a flowtable tries to
offload a flow through the tunnel. That routing loop is a configuration
any CAP_NET_ADMIN user can set up, and ip_tunnel_xmit() and
ip6_tnl_xmit() already treat it as a tx error, so remove the warning and
just fail the walk, as commit 008e7a7c293b (&amp;#34;net: remove WARN_ON_ONCE
when accessing forward path array&amp;#34;) did for the path stack overflow.&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;net: remove WARN_ON_ONCE() from the dev_fill_forward_path() loop check&lt;/p&gt;
&lt;p&gt;ipip_fill_forward_path() and ip6_tnl_fill_forward_path() look up the
route to the tunnel&amp;#39;s remote endpoint and set ctx-&amp;gt;dev to its device,
which is the tunnel itself when that route resolves back to the tunnel.
dev_fill_forward_path() then makes no progress and trips
WARN_ON_ONCE(last_dev == ctx-&amp;gt;dev) as soon as a flowtable tries to
offload a flow through the tunnel. That routing loop is a configuration
any CAP_NET_ADMIN user can set up, and ip_tunnel_xmit() and
ip6_tnl_xmit() already treat it as a tx error, so remove the warning and
just fail the walk, as commit 008e7a7c293b (&amp;#34;net: remove WARN_ON_ONCE
when accessing forward path array&amp;#34;) did for the path stack overflow.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-98278</guid>
    </item>
    <item>
      <title>GHSA-6vfc-qfc9-vf68</title>
      <link>https://db.gcve.eu/vuln/ghsa-6vfc-qfc9-vf68</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;net: remove WARN_ON_ONCE() from the dev_fill_forward_path() loop check&lt;/p&gt;
&lt;p&gt;ipip_fill_forward_path() and ip6_tnl_fill_forward_path() look up the
route to the tunnel&amp;#39;s remote endpoint and set ctx-&amp;gt;dev to its device,
which is the tunnel itself when that route resolves back to the tunnel.
dev_fill_forward_path() then makes no progress and trips
WARN_ON_ONCE(last_dev == ctx-&amp;gt;dev) as soon as a flowtable tries to
offload a flow through the tunnel. That routing loop is a configuration
any CAP_NET_ADMIN user can set up, and ip_tunnel_xmit() and
ip6_tnl_xmit() already treat it as a tx error, so remove the warning and
just fail the walk, as commit 008e7a7c293b (&amp;#34;net: remove WARN_ON_ONCE
when accessing forward path array&amp;#34;) did for the path stack overflow.&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;net: remove WARN_ON_ONCE() from the dev_fill_forward_path() loop check&lt;/p&gt;
&lt;p&gt;ipip_fill_forward_path() and ip6_tnl_fill_forward_path() look up the
route to the tunnel&amp;#39;s remote endpoint and set ctx-&amp;gt;dev to its device,
which is the tunnel itself when that route resolves back to the tunnel.
dev_fill_forward_path() then makes no progress and trips
WARN_ON_ONCE(last_dev == ctx-&amp;gt;dev) as soon as a flowtable tries to
offload a flow through the tunnel. That routing loop is a configuration
any CAP_NET_ADMIN user can set up, and ip_tunnel_xmit() and
ip6_tnl_xmit() already treat it as a tx error, so remove the warning and
just fail the walk, as commit 008e7a7c293b (&amp;#34;net: remove WARN_ON_ONCE
when accessing forward path array&amp;#34;) did for the path stack overflow.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-6vfc-qfc9-vf68</guid>
    </item>
    <item>
      <title>openSUSE-SU-2026:12131-1 — kernel-devel-7.2.10-1.1 on GA media</title>
      <link>https://db.gcve.eu/vuln/opensuse-su-2026:12131-1</link>
      <description>&lt;p&gt;kernel-devel-7.2.10-1.1 on GA media&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel-devel-7.2.10-1.1 on GA media&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/opensuse-su-2026:12131-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-98278</title>
      <link>https://db.gcve.eu/vuln/ubuntu-cve-2026-98278</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 118 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: net: remove WARN_ON_ONCE() from the dev_fill_forward_path() loop check ipip_fill_forward_path() and ip6_tnl_fill_forward_path() look up the route to the tunnel&amp;#39;s remote endpoint and set ctx-&amp;gt;dev to its device, which is the tunnel itself when that route resolves back to the tunnel. dev_fill_forward_path() then makes no progress and trips WARN_ON_ONCE(last_dev == ctx-&amp;gt;dev) as soon as a flowtable tries to offload a flow through the tunnel. That routing loop is a configuration any CAP_NET_ADMIN user can set up, and ip_tunnel_xmit() and ip6_tnl_xmit() already treat it as a tx error, so remove the warning and just fail the walk, as commit 008e7a7c293b (&amp;#34;net: remove WARN_ON_ONCE when accessing forward path array&amp;#34;) did for the path stack overflow.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 118 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: net: remove WARN_ON_ONCE() from the dev_fill_forward_path() loop check ipip_fill_forward_path() and ip6_tnl_fill_forward_path() look up the route to the tunnel&amp;#39;s remote endpoint and set ctx-&amp;gt;dev to its device, which is the tunnel itself when that route resolves back to the tunnel. dev_fill_forward_path() then makes no progress and trips WARN_ON_ONCE(last_dev == ctx-&amp;gt;dev) as soon as a flowtable tries to offload a flow through the tunnel. That routing loop is a configuration any CAP_NET_ADMIN user can set up, and ip_tunnel_xmit() and ip6_tnl_xmit() already treat it as a tx error, so remove the warning and just fail the walk, as commit 008e7a7c293b (&amp;#34;net: remove WARN_ON_ONCE when accessing forward path array&amp;#34;) did for the path stack overflow.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ubuntu-cve-2026-98278</guid>
    </item>
  </channel>
</rss>
