<?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>Sun, 04 Oct 2026 09:10:24 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-36244 — net/sched: taprio: extend minimum interval restriction to entire cycle too</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2024-36244</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: taprio: extend minimum interval restriction to entire cycle too&lt;/p&gt;
&lt;p&gt;It is possible for syzbot to side-step the restriction imposed by the
blamed commit in the Fixes: tag, because the taprio UAPI permits a
cycle-time different from (and potentially shorter than) the sum of
entry intervals.&lt;/p&gt;
&lt;p&gt;We need one more restriction, which is that the cycle time itself must
be larger than N * ETH_ZLEN bit times, where N is the number of schedule
entries. This restriction needs to apply regardless of whether the cycle
time came from the user or was the implicit, auto-calculated value, so
we move the existing &amp;#34;cycle == 0&amp;#34; check outside the &amp;#34;if &amp;#34;(!new-&amp;gt;cycle_time)&amp;#34;
branch. This way covers both conditions and scenarios.&lt;/p&gt;
&lt;p&gt;Add a selftest which illustrates the issue triggered by syzbot.&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: taprio: extend minimum interval restriction to entire cycle too&lt;/p&gt;
&lt;p&gt;It is possible for syzbot to side-step the restriction imposed by the
blamed commit in the Fixes: tag, because the taprio UAPI permits a
cycle-time different from (and potentially shorter than) the sum of
entry intervals.&lt;/p&gt;
&lt;p&gt;We need one more restriction, which is that the cycle time itself must
be larger than N * ETH_ZLEN bit times, where N is the number of schedule
entries. This restriction needs to apply regardless of whether the cycle
time came from the user or was the implicit, auto-calculated value, so
we move the existing &amp;#34;cycle == 0&amp;#34; check outside the &amp;#34;if &amp;#34;(!new-&amp;gt;cycle_time)&amp;#34;
branch. This way covers both conditions and scenarios.&lt;/p&gt;
&lt;p&gt;Add a selftest which illustrates the issue triggered by syzbot.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2024-36244</guid>
    </item>
  </channel>
</rss>
