<?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>Wed, 30 Sep 2026 16:00:07 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-74543 — net: udp_tunnel: fix memory leak in udp_tunnel_nic_unregister()</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-74543</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: udp_tunnel: fix memory leak in udp_tunnel_nic_unregister()&lt;/p&gt;
&lt;p&gt;syzbot reported a memory leak [1] in the UDP tunnel NIC offload code.&lt;/p&gt;
&lt;p&gt;When device registration fails (e.g. in register_netdevice()), netdev core
unwinds by sending a single NETDEV_UNREGISTER notification. If work was queued
during NETDEV_REGISTER (utn-&amp;gt;work_pending is set), udp_tunnel_nic_unregister()
returns early:&lt;/p&gt;
&lt;p&gt;if (utn-&amp;gt;work_pending)
		return;&lt;/p&gt;
&lt;p&gt;Because failed registrations do not enter netdev_wait_allrefs_any(), no
subsequent NETDEV_UNREGISTER rebroadcast will ever occur. As a result, the
struct udp_tunnel_nic allocated in udp_tunnel_nic_alloc() is leaked
permanently.&lt;/p&gt;
&lt;p&gt;Fix this by removing the early return. Instead, synchronously cancel any
pending work with cancel_delayed_work_sync() before freeing @utn.&lt;/p&gt;
&lt;p&gt;To be able to call cancel_delayed_work_sync() while holding RTNL (the work also
needs RTNL), switch udp_tunnel_nic_device_sync_work() to rtnl_trylock(). If RTNL
is contended, requeue the work with a 1 jiffy delay (via queue_delayed_work())
to prevent high CPU contention while waiting for RTNL lock.&lt;/p&gt;
&lt;p&gt;The utn-&amp;gt;work_pending bookkeeping is no longer needed and is removed, as
the workqueue core already tracks the pending/running state of the work.&lt;/p&gt;
&lt;p&gt;[1]
BUG: memory leak
unreferenced object 0xffff888127d5f840 (size 96):
  comm &amp;#34;syz-executor&amp;#34;, pid 5806, jiffies 4294942188
  backtrace (crc 99fdb6c8):
    __kmalloc_noprof+0x3bf/0x550
    udp_t…&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: udp_tunnel: fix memory leak in udp_tunnel_nic_unregister()&lt;/p&gt;
&lt;p&gt;syzbot reported a memory leak [1] in the UDP tunnel NIC offload code.&lt;/p&gt;
&lt;p&gt;When device registration fails (e.g. in register_netdevice()), netdev core
unwinds by sending a single NETDEV_UNREGISTER notification. If work was queued
during NETDEV_REGISTER (utn-&amp;gt;work_pending is set), udp_tunnel_nic_unregister()
returns early:&lt;/p&gt;
&lt;p&gt;if (utn-&amp;gt;work_pending)
		return;&lt;/p&gt;
&lt;p&gt;Because failed registrations do not enter netdev_wait_allrefs_any(), no
subsequent NETDEV_UNREGISTER rebroadcast will ever occur. As a result, the
struct udp_tunnel_nic allocated in udp_tunnel_nic_alloc() is leaked
permanently.&lt;/p&gt;
&lt;p&gt;Fix this by removing the early return. Instead, synchronously cancel any
pending work with cancel_delayed_work_sync() before freeing @utn.&lt;/p&gt;
&lt;p&gt;To be able to call cancel_delayed_work_sync() while holding RTNL (the work also
needs RTNL), switch udp_tunnel_nic_device_sync_work() to rtnl_trylock(). If RTNL
is contended, requeue the work with a 1 jiffy delay (via queue_delayed_work())
to prevent high CPU contention while waiting for RTNL lock.&lt;/p&gt;
&lt;p&gt;The utn-&amp;gt;work_pending bookkeeping is no longer needed and is removed, as
the workqueue core already tracks the pending/running state of the work.&lt;/p&gt;
&lt;p&gt;[1]
BUG: memory leak
unreferenced object 0xffff888127d5f840 (size 96):
  comm &amp;#34;syz-executor&amp;#34;, pid 5806, jiffies 4294942188
  backtrace (crc 99fdb6c8):
    __kmalloc_noprof+0x3bf/0x550
    udp_t…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-74543</guid>
    </item>
  </channel>
</rss>
