<?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>Tue, 29 Sep 2026 04:55:57 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-90075 — net/sched: fq_codel: clamp default quantum and mtu</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-90075</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: fq_codel: clamp default quantum and mtu&lt;/p&gt;
&lt;p&gt;fq_codel_init() sets q-&amp;gt;quantum = psched_mtu(qdisc_dev(sch)) without
clamping. A device with a huge MTU (e.g. dummy with max_mtu == 0
accepting MTU 2147483634) makes psched_mtu() return 0x80000000, which
overflows the signed flow-&amp;gt;deficit to INT_MIN in fq_codel_dequeue(),
causing an infinite loop and soft lockup. Emulate fq_codel_change()
and constrain to [256, FQ_CODEL_QUANTUM_MAX].&lt;/p&gt;
&lt;p&gt;The same unclamped psched_mtu() is assigned to q-&amp;gt;cparams.mtu a bit
below, and fq_codel_change() never updates it. codel_should_drop()
tests &amp;#34;*backlog &amp;lt;= params-&amp;gt;mtu&amp;#34;; with mtu == 0x80000000 (~2 GiB) and
the default 32 MiB memory_limit, the test is always true, so CoDel is
silently and completely disabled (no drops, no ECN). Declare a single
clamped mtu and assign both q-&amp;gt;quantum and q-&amp;gt;cparams.mtu from it,
which also removes the double psched_mtu() call.&lt;/p&gt;
&lt;p&gt;Conditions to recreate the bug: a device whose MTU (plus
hard_header_len) wraps psched_mtu() into the sign bit (e.g. a dummy
device with max_mtu == 0 accepting MTU 2147483634). Requires
CAP_NET_ADMIN in a user namespace.&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: fq_codel: clamp default quantum and mtu&lt;/p&gt;
&lt;p&gt;fq_codel_init() sets q-&amp;gt;quantum = psched_mtu(qdisc_dev(sch)) without
clamping. A device with a huge MTU (e.g. dummy with max_mtu == 0
accepting MTU 2147483634) makes psched_mtu() return 0x80000000, which
overflows the signed flow-&amp;gt;deficit to INT_MIN in fq_codel_dequeue(),
causing an infinite loop and soft lockup. Emulate fq_codel_change()
and constrain to [256, FQ_CODEL_QUANTUM_MAX].&lt;/p&gt;
&lt;p&gt;The same unclamped psched_mtu() is assigned to q-&amp;gt;cparams.mtu a bit
below, and fq_codel_change() never updates it. codel_should_drop()
tests &amp;#34;*backlog &amp;lt;= params-&amp;gt;mtu&amp;#34;; with mtu == 0x80000000 (~2 GiB) and
the default 32 MiB memory_limit, the test is always true, so CoDel is
silently and completely disabled (no drops, no ECN). Declare a single
clamped mtu and assign both q-&amp;gt;quantum and q-&amp;gt;cparams.mtu from it,
which also removes the double psched_mtu() call.&lt;/p&gt;
&lt;p&gt;Conditions to recreate the bug: a device whose MTU (plus
hard_header_len) wraps psched_mtu() into the sign bit (e.g. a dummy
device with max_mtu == 0 accepting MTU 2147483634). Requires
CAP_NET_ADMIN in a user namespace.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-90075</guid>
    </item>
  </channel>
</rss>
