<?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>Wed, 07 Oct 2026 13:53:43 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-63982 — net/sched: Fix ethx:ingress -&gt; ethy:egress -&gt; ethx:ingress mirred loop</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-63982</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;net/sched: Fix ethx:ingress -&amp;gt; ethy:egress -&amp;gt; ethx:ingress mirred loop&lt;/p&gt;
&lt;p&gt;When mirred redirects to ingress (from either ingress or egress) the loop
state from sched_mirred_dev array dev is lost because of 1) the packet
deferral into the backlog and 2) the fact the sched_mirred_dev array is
cleared. In such cases, if there was a loop we won&amp;#39;t discover it.&lt;/p&gt;
&lt;p&gt;Here&amp;#39;s a simple test to reproduce:
ip a add dev port0 10.10.10.11/24&lt;/p&gt;
&lt;p&gt;tc qdisc add dev port0 clsact
tc filter add dev port0 egress protocol ip \
   prio 10 matchall action mirred ingress redirect dev port1&lt;/p&gt;
&lt;p&gt;tc qdisc add dev port1 clsact
tc filter add dev port1 ingress protocol ip \
   prio 10 matchall action mirred egress redirect dev port0&lt;/p&gt;
&lt;p&gt;ping -c 1 -W0.01 10.10.10.10&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;net/sched: Fix ethx:ingress -&amp;gt; ethy:egress -&amp;gt; ethx:ingress mirred loop&lt;/p&gt;
&lt;p&gt;When mirred redirects to ingress (from either ingress or egress) the loop
state from sched_mirred_dev array dev is lost because of 1) the packet
deferral into the backlog and 2) the fact the sched_mirred_dev array is
cleared. In such cases, if there was a loop we won&amp;#39;t discover it.&lt;/p&gt;
&lt;p&gt;Here&amp;#39;s a simple test to reproduce:
ip a add dev port0 10.10.10.11/24&lt;/p&gt;
&lt;p&gt;tc qdisc add dev port0 clsact
tc filter add dev port0 egress protocol ip \
   prio 10 matchall action mirred ingress redirect dev port1&lt;/p&gt;
&lt;p&gt;tc qdisc add dev port1 clsact
tc filter add dev port1 ingress protocol ip \
   prio 10 matchall action mirred egress redirect dev port0&lt;/p&gt;
&lt;p&gt;ping -c 1 -W0.01 10.10.10.10&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-63982</guid>
    </item>
  </channel>
</rss>
