<?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 15:59:27 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-80615 — net: dst_metadata: fix false-positive memcpy overflow in tun_dst_unclone</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-80615</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: dst_metadata: fix false-positive memcpy overflow in tun_dst_unclone&lt;/p&gt;
&lt;p&gt;kmalloc_flex() in metadata_dst_alloc() sets __counted_by for the
structure to the options_len, which is then initialized to zero.
Later, we&amp;#39;re initializing the structure by copying the tunnel info
together with the options, and this triggers a warning for a potential
memcpy overflow, since the compiler estimates that the options can&amp;#39;t
fit into the structure, even though the memory for them is actually
allocated.&lt;/p&gt;
&lt;p&gt;memcpy: detected buffer overflow: 104 byte write of buffer size 96
 WARNING: CPU: X PID: Y at lib/string_helpers.c:1036 __fortify_report
  skb_tunnel_info_unclone+0x179/0x190
  geneve_xmit+0x7fe/0xe00&lt;/p&gt;
&lt;p&gt;The issue is triggered when built with clang and source fortification.&lt;/p&gt;
&lt;p&gt;Fix that by doing the copy in two stages: first - the main data with
the options_len, then the options.  This way the correct length should
be known at the time of the copy.&lt;/p&gt;
&lt;p&gt;It would be better if the options_len never changed after allocation,
but the allocation code is a little separate from the initialization
and it would be awkward and potentially dangerous to return a struct
with options_len set to a non-zero value from the metadata_dst_alloc().&lt;/p&gt;
&lt;p&gt;Another option would be to use ip_tunnel_info_opts_set(), but it is
doing too many unnecessary operations for the use case here.&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: dst_metadata: fix false-positive memcpy overflow in tun_dst_unclone&lt;/p&gt;
&lt;p&gt;kmalloc_flex() in metadata_dst_alloc() sets __counted_by for the
structure to the options_len, which is then initialized to zero.
Later, we&amp;#39;re initializing the structure by copying the tunnel info
together with the options, and this triggers a warning for a potential
memcpy overflow, since the compiler estimates that the options can&amp;#39;t
fit into the structure, even though the memory for them is actually
allocated.&lt;/p&gt;
&lt;p&gt;memcpy: detected buffer overflow: 104 byte write of buffer size 96
 WARNING: CPU: X PID: Y at lib/string_helpers.c:1036 __fortify_report
  skb_tunnel_info_unclone+0x179/0x190
  geneve_xmit+0x7fe/0xe00&lt;/p&gt;
&lt;p&gt;The issue is triggered when built with clang and source fortification.&lt;/p&gt;
&lt;p&gt;Fix that by doing the copy in two stages: first - the main data with
the options_len, then the options.  This way the correct length should
be known at the time of the copy.&lt;/p&gt;
&lt;p&gt;It would be better if the options_len never changed after allocation,
but the allocation code is a little separate from the initialization
and it would be awkward and potentially dangerous to return a struct
with options_len set to a non-zero value from the metadata_dst_alloc().&lt;/p&gt;
&lt;p&gt;Another option would be to use ip_tunnel_info_opts_set(), but it is
doing too many unnecessary operations for the use case here.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-80615</guid>
    </item>
  </channel>
</rss>
