<?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, 06 Oct 2026 15:25:02 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-23095 — gue: Fix skb memleak with inner IP protocol 0.</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-23095</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux, Siemens SIMATIC S7-1500 CPU 1518-4 PN/DP MFP, Siemens SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP, Siemens SIPLUS S7-1500 CPU 1518-4 PN/DP MFP&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;gue: Fix skb memleak with inner IP protocol 0.&lt;/p&gt;
&lt;p&gt;syzbot reported skb memleak below. [0]&lt;/p&gt;
&lt;p&gt;The repro generated a GUE packet with its inner protocol 0.&lt;/p&gt;
&lt;p&gt;gue_udp_recv() returns -guehdr-&amp;gt;proto_ctype for &amp;#34;resubmit&amp;#34;
in ip_protocol_deliver_rcu(), but this only works with
non-zero protocol number.&lt;/p&gt;
&lt;p&gt;Let&amp;#39;s drop such packets.&lt;/p&gt;
&lt;p&gt;Note that 0 is a valid number (IPv6 Hop-by-Hop Option).&lt;/p&gt;
&lt;p&gt;I think it is not practical to encap HOPOPT in GUE, so once
someone starts to complain, we could pass down a resubmit
flag pointer to distinguish two zeros from the upper layer:&lt;/p&gt;
&lt;p&gt;* no error
  * resubmit HOPOPT&lt;/p&gt;
&lt;p&gt;[0]
BUG: memory leak
unreferenced object 0xffff888109695a00 (size 240):
  comm &amp;#34;syz.0.17&amp;#34;, pid 6088, jiffies 4294943096
  hex dump (first 32 bytes):
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
    00 40 c2 10 81 88 ff ff 00 00 00 00 00 00 00 00  .@..............
  backtrace (crc a84b336f):
    kmemleak_alloc_recursive include/linux/kmemleak.h:44 [inline]
    slab_post_alloc_hook mm/slub.c:4958 [inline]
    slab_alloc_node mm/slub.c:5263 [inline]
    kmem_cache_alloc_noprof+0x3b4/0x590 mm/slub.c:5270
    __build_skb+0x23/0x60 net/core/skbuff.c:474
    build_skb+0x20/0x190 net/core/skbuff.c:490
    __tun_build_skb drivers/net/tun.c:1541 [inline]
    tun_build_skb+0x4a1/0xa40 drivers/net/tun.c:1636
    tun_get_user+0xc12/0x2030 drivers/net/tun.c:1770
    tun_chr_write_iter+0x71/0x120 drivers/net/tun.c:1999…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux, Siemens SIMATIC S7-1500 CPU 1518-4 PN/DP MFP, Siemens SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP, Siemens SIPLUS S7-1500 CPU 1518-4 PN/DP MFP&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;gue: Fix skb memleak with inner IP protocol 0.&lt;/p&gt;
&lt;p&gt;syzbot reported skb memleak below. [0]&lt;/p&gt;
&lt;p&gt;The repro generated a GUE packet with its inner protocol 0.&lt;/p&gt;
&lt;p&gt;gue_udp_recv() returns -guehdr-&amp;gt;proto_ctype for &amp;#34;resubmit&amp;#34;
in ip_protocol_deliver_rcu(), but this only works with
non-zero protocol number.&lt;/p&gt;
&lt;p&gt;Let&amp;#39;s drop such packets.&lt;/p&gt;
&lt;p&gt;Note that 0 is a valid number (IPv6 Hop-by-Hop Option).&lt;/p&gt;
&lt;p&gt;I think it is not practical to encap HOPOPT in GUE, so once
someone starts to complain, we could pass down a resubmit
flag pointer to distinguish two zeros from the upper layer:&lt;/p&gt;
&lt;p&gt;* no error
  * resubmit HOPOPT&lt;/p&gt;
&lt;p&gt;[0]
BUG: memory leak
unreferenced object 0xffff888109695a00 (size 240):
  comm &amp;#34;syz.0.17&amp;#34;, pid 6088, jiffies 4294943096
  hex dump (first 32 bytes):
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
    00 40 c2 10 81 88 ff ff 00 00 00 00 00 00 00 00  .@..............
  backtrace (crc a84b336f):
    kmemleak_alloc_recursive include/linux/kmemleak.h:44 [inline]
    slab_post_alloc_hook mm/slub.c:4958 [inline]
    slab_alloc_node mm/slub.c:5263 [inline]
    kmem_cache_alloc_noprof+0x3b4/0x590 mm/slub.c:5270
    __build_skb+0x23/0x60 net/core/skbuff.c:474
    build_skb+0x20/0x190 net/core/skbuff.c:490
    __tun_build_skb drivers/net/tun.c:1541 [inline]
    tun_build_skb+0x4a1/0xa40 drivers/net/tun.c:1636
    tun_get_user+0xc12/0x2030 drivers/net/tun.c:1770
    tun_chr_write_iter+0x71/0x120 drivers/net/tun.c:1999…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-23095</guid>
    </item>
  </channel>
</rss>
