<?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 16:45:09 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-80793 — ipv4: reject undersized MTUs in ip_do_fragment()</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-80793</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;ipv4: reject undersized MTUs in ip_do_fragment()&lt;/p&gt;
&lt;p&gt;ip_do_fragment() subtracts the IPv4 header length from the effective
MTU and passes the resulting payload MTU to ip_frag_next().&lt;/p&gt;
&lt;p&gt;If the effective MTU is smaller than hlen + 8, ip_frag_next() rounds
the fragment payload length down to zero. The fragmentation state then
never makes forward progress: state-&amp;gt;left, state-&amp;gt;ptr and state-&amp;gt;offset
stay unchanged while ip_do_fragment() keeps allocating and transmitting
header-only fragments until the softlockup detector fires.&lt;/p&gt;
&lt;p&gt;This is reproducible with a route installed using &amp;#34;mtu lock 20&amp;#34;, but it
is also reproducible without route MTU lock, for example by forwarding a
packet to a device whose MTU is 20.&lt;/p&gt;
&lt;p&gt;Fix it in ip_do_fragment() by rejecting mtu &amp;lt; hlen + 8 with -EMSGSIZE,
matching the existing IPv6 fragmentation check.&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;ipv4: reject undersized MTUs in ip_do_fragment()&lt;/p&gt;
&lt;p&gt;ip_do_fragment() subtracts the IPv4 header length from the effective
MTU and passes the resulting payload MTU to ip_frag_next().&lt;/p&gt;
&lt;p&gt;If the effective MTU is smaller than hlen + 8, ip_frag_next() rounds
the fragment payload length down to zero. The fragmentation state then
never makes forward progress: state-&amp;gt;left, state-&amp;gt;ptr and state-&amp;gt;offset
stay unchanged while ip_do_fragment() keeps allocating and transmitting
header-only fragments until the softlockup detector fires.&lt;/p&gt;
&lt;p&gt;This is reproducible with a route installed using &amp;#34;mtu lock 20&amp;#34;, but it
is also reproducible without route MTU lock, for example by forwarding a
packet to a device whose MTU is 20.&lt;/p&gt;
&lt;p&gt;Fix it in ip_do_fragment() by rejecting mtu &amp;lt; hlen + 8 with -EMSGSIZE,
matching the existing IPv6 fragmentation check.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-80793</guid>
    </item>
  </channel>
</rss>
