<?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 11:08:34 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-71128 — erspan: Initialize options_len before referencing options.</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2025-71128</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;erspan: Initialize options_len before referencing options.&lt;/p&gt;
&lt;p&gt;The struct ip_tunnel_info has a flexible array member named
options that is protected by a counted_by(options_len)
attribute.&lt;/p&gt;
&lt;p&gt;The compiler will use this information to enforce runtime bounds
checking deployed by FORTIFY_SOURCE string helpers.&lt;/p&gt;
&lt;p&gt;As laid out in the GCC documentation, the counter must be
initialized before the first reference to the flexible array
member.&lt;/p&gt;
&lt;p&gt;After scanning through the files that use struct ip_tunnel_info
and also refer to options or options_len, it appears the normal
case is to use the ip_tunnel_info_opts_set() helper.&lt;/p&gt;
&lt;p&gt;Said helper would initialize options_len properly before copying
data into options, however in the GRE ERSPAN code a partial
update is done, preventing the use of the helper function.&lt;/p&gt;
&lt;p&gt;Before this change the handling of ERSPAN traffic in GRE tunnels
would cause a kernel panic when the kernel is compiled with
GCC 15+ and having FORTIFY_SOURCE configured:&lt;/p&gt;
&lt;p&gt;memcpy: detected buffer overflow: 4 byte write of buffer size 0&lt;/p&gt;
&lt;p&gt;Call Trace:
 &amp;lt;IRQ&amp;gt;
 __fortify_panic+0xd/0xf
 erspan_rcv.cold+0x68/0x83
 ? ip_route_input_slow+0x816/0x9d0
 gre_rcv+0x1b2/0x1c0
 gre_rcv+0x8e/0x100
 ? raw_v4_input+0x2a0/0x2b0
 ip_protocol_deliver_rcu+0x1ea/0x210
 ip_local_deliver_finish+0x86/0x110
 ip_local_deliver+0x65/0x110
 ? ip_rcv_finish_core+0xd6/0x360
 ip_rcv+0x186/0x1a0&lt;/p&gt;
&lt;p&gt;Reported-at: https://launchpad.net/bugs/2129580&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;erspan: Initialize options_len before referencing options.&lt;/p&gt;
&lt;p&gt;The struct ip_tunnel_info has a flexible array member named
options that is protected by a counted_by(options_len)
attribute.&lt;/p&gt;
&lt;p&gt;The compiler will use this information to enforce runtime bounds
checking deployed by FORTIFY_SOURCE string helpers.&lt;/p&gt;
&lt;p&gt;As laid out in the GCC documentation, the counter must be
initialized before the first reference to the flexible array
member.&lt;/p&gt;
&lt;p&gt;After scanning through the files that use struct ip_tunnel_info
and also refer to options or options_len, it appears the normal
case is to use the ip_tunnel_info_opts_set() helper.&lt;/p&gt;
&lt;p&gt;Said helper would initialize options_len properly before copying
data into options, however in the GRE ERSPAN code a partial
update is done, preventing the use of the helper function.&lt;/p&gt;
&lt;p&gt;Before this change the handling of ERSPAN traffic in GRE tunnels
would cause a kernel panic when the kernel is compiled with
GCC 15+ and having FORTIFY_SOURCE configured:&lt;/p&gt;
&lt;p&gt;memcpy: detected buffer overflow: 4 byte write of buffer size 0&lt;/p&gt;
&lt;p&gt;Call Trace:
 &amp;lt;IRQ&amp;gt;
 __fortify_panic+0xd/0xf
 erspan_rcv.cold+0x68/0x83
 ? ip_route_input_slow+0x816/0x9d0
 gre_rcv+0x1b2/0x1c0
 gre_rcv+0x8e/0x100
 ? raw_v4_input+0x2a0/0x2b0
 ip_protocol_deliver_rcu+0x1ea/0x210
 ip_local_deliver_finish+0x86/0x110
 ip_local_deliver+0x65/0x110
 ? ip_rcv_finish_core+0xd6/0x360
 ip_rcv+0x186/0x1a0&lt;/p&gt;
&lt;p&gt;Reported-at: https://launchpad.net/bugs/2129580&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2025-71128</guid>
    </item>
  </channel>
</rss>
