<?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 19:34:18 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-63983 — net/sched: fix packet loop on netem when duplicate is on</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-63983</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 packet loop on netem when duplicate is on&lt;/p&gt;
&lt;p&gt;When netem duplicates a packet it re-enqueues the copy at the root qdisc.
If another netem sits in the tree the copy can be duplicated
again, recursing until the stack or memory is exhausted.&lt;/p&gt;
&lt;p&gt;The original duplication guard temporarily zeroed q-&amp;gt;duplicate around
the re-enqueue, but that does not cover all cases because it is
per-qdisc state shared across all concurrent enqueue paths
and is not safe without additional locking.&lt;/p&gt;
&lt;p&gt;Use the skb tc_depth field introduced in an earlier patch:
 - increment it on the duplicate before re-enqueue
 - skip duplication for any skb whose tc_depth is already non-zero.&lt;/p&gt;
&lt;p&gt;This marks the packet itself rather than mutating qdisc state,
therefore it is safe regardless of tree topology or concurrency.&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 packet loop on netem when duplicate is on&lt;/p&gt;
&lt;p&gt;When netem duplicates a packet it re-enqueues the copy at the root qdisc.
If another netem sits in the tree the copy can be duplicated
again, recursing until the stack or memory is exhausted.&lt;/p&gt;
&lt;p&gt;The original duplication guard temporarily zeroed q-&amp;gt;duplicate around
the re-enqueue, but that does not cover all cases because it is
per-qdisc state shared across all concurrent enqueue paths
and is not safe without additional locking.&lt;/p&gt;
&lt;p&gt;Use the skb tc_depth field introduced in an earlier patch:
 - increment it on the duplicate before re-enqueue
 - skip duplication for any skb whose tc_depth is already non-zero.&lt;/p&gt;
&lt;p&gt;This marks the packet itself rather than mutating qdisc state,
therefore it is safe regardless of tree topology or concurrency.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-63983</guid>
    </item>
  </channel>
</rss>
