<?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://db.gcve.eu</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, 05 Nov 2026 07:14:06 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-99246</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-99246</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;tipc: protect node reset trace dump with node lock&lt;/p&gt;
&lt;p&gt;The tipc_node_reset_links trace event asks tipc_node_dump() to walk the
node&amp;#39;s link entries. Unlike the other node events that request link data,
this event runs without the node lock.&lt;/p&gt;
&lt;p&gt;This permits bearer teardown to free a link while the trace callback is
dumping it:&lt;/p&gt;
&lt;p&gt;CPU 0                                CPU 1
  trace_tipc_node_reset_links()
    tipc_node_dump()
      l = n-&amp;gt;links[0].link
                                       tipc_node_write_lock()
                                       kfree(l)
                                       n-&amp;gt;links[0].link = NULL
                                       tipc_node_write_unlock()
      tipc_link_dump(l)&lt;/p&gt;
&lt;p&gt;tipc_link_dump() then dereferences the stale pointer. KASAN reported:&lt;/p&gt;
&lt;p&gt;BUG: KASAN: slab-use-after-free in tipc_link_dump
  Read of size 4 by task poc/115
  Call Trace:
   tipc_link_dump+0x10cb/0x16b0
   tipc_node_dump+0x4bb/0x740
   trace_event_raw_event_tipc_node_class+0x258/0x360
   tipc_node_reset_links+0x14d/0x1a0
   tipc_rcv+0x13f5/0x3030
   tipc_udp_recv+0x4e3/0x670
  Allocated by task 0:
   tipc_link_create+0x1e1/0x1020
   tipc_node_check_dest+0x7d2/0x11a0
   tipc_disc_rcv+0xdbf/0x1430
  Freed by task 89:
   kfree+0x131/0x3c0
   tipc_node_link_down+0x267/0x4b0
   tipc_node_delete_links+0xec/0x160
   bearer_disable+0x107/0x260&lt;/p&gt;
&lt;p&gt;Take the node write lock around the trace event. This serializes the
dump ag…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;tipc: protect node reset trace dump with node lock&lt;/p&gt;
&lt;p&gt;The tipc_node_reset_links trace event asks tipc_node_dump() to walk the
node&amp;#39;s link entries. Unlike the other node events that request link data,
this event runs without the node lock.&lt;/p&gt;
&lt;p&gt;This permits bearer teardown to free a link while the trace callback is
dumping it:&lt;/p&gt;
&lt;p&gt;CPU 0                                CPU 1
  trace_tipc_node_reset_links()
    tipc_node_dump()
      l = n-&amp;gt;links[0].link
                                       tipc_node_write_lock()
                                       kfree(l)
                                       n-&amp;gt;links[0].link = NULL
                                       tipc_node_write_unlock()
      tipc_link_dump(l)&lt;/p&gt;
&lt;p&gt;tipc_link_dump() then dereferences the stale pointer. KASAN reported:&lt;/p&gt;
&lt;p&gt;BUG: KASAN: slab-use-after-free in tipc_link_dump
  Read of size 4 by task poc/115
  Call Trace:
   tipc_link_dump+0x10cb/0x16b0
   tipc_node_dump+0x4bb/0x740
   trace_event_raw_event_tipc_node_class+0x258/0x360
   tipc_node_reset_links+0x14d/0x1a0
   tipc_rcv+0x13f5/0x3030
   tipc_udp_recv+0x4e3/0x670
  Allocated by task 0:
   tipc_link_create+0x1e1/0x1020
   tipc_node_check_dest+0x7d2/0x11a0
   tipc_disc_rcv+0xdbf/0x1430
  Freed by task 89:
   kfree+0x131/0x3c0
   tipc_node_link_down+0x267/0x4b0
   tipc_node_delete_links+0xec/0x160
   bearer_disable+0x107/0x260&lt;/p&gt;
&lt;p&gt;Take the node write lock around the trace event. This serializes the
dump ag…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-99246</guid>
    </item>
    <item>
      <title>GHSA-qwfh-hpch-ph73</title>
      <link>https://db.gcve.eu/vuln/ghsa-qwfh-hpch-ph73</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;tipc: protect node reset trace dump with node lock&lt;/p&gt;
&lt;p&gt;The tipc_node_reset_links trace event asks tipc_node_dump() to walk the
node&amp;#39;s link entries. Unlike the other node events that request link data,
this event runs without the node lock.&lt;/p&gt;
&lt;p&gt;This permits bearer teardown to free a link while the trace callback is
dumping it:&lt;/p&gt;
&lt;p&gt;CPU 0                                CPU 1
  trace_tipc_node_reset_links()
    tipc_node_dump()
      l = n-&amp;gt;links[0].link
                                       tipc_node_write_lock()
                                       kfree(l)
                                       n-&amp;gt;links[0].link = NULL
                                       tipc_node_write_unlock()
      tipc_link_dump(l)&lt;/p&gt;
&lt;p&gt;tipc_link_dump() then dereferences the stale pointer. KASAN reported:&lt;/p&gt;
&lt;p&gt;BUG: KASAN: slab-use-after-free in tipc_link_dump
  Read of size 4 by task poc/115
  Call Trace:
   tipc_link_dump+0x10cb/0x16b0
   tipc_node_dump+0x4bb/0x740
   trace_event_raw_event_tipc_node_class+0x258/0x360
   tipc_node_reset_links+0x14d/0x1a0
   tipc_rcv+0x13f5/0x3030
   tipc_udp_recv+0x4e3/0x670
  Allocated by task 0:
   tipc_link_create+0x1e1/0x1020
   tipc_node_check_dest+0x7d2/0x11a0
   tipc_disc_rcv+0xdbf/0x1430
  Freed by task 89:
   kfree+0x131/0x3c0
   tipc_node_link_down+0x267/0x4b0
   tipc_node_delete_links+0xec/0x160
   bearer_disable+0x107/0x260&lt;/p&gt;
&lt;p&gt;Take the node write lock around the trace event. This serializes the
dump ag…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;tipc: protect node reset trace dump with node lock&lt;/p&gt;
&lt;p&gt;The tipc_node_reset_links trace event asks tipc_node_dump() to walk the
node&amp;#39;s link entries. Unlike the other node events that request link data,
this event runs without the node lock.&lt;/p&gt;
&lt;p&gt;This permits bearer teardown to free a link while the trace callback is
dumping it:&lt;/p&gt;
&lt;p&gt;CPU 0                                CPU 1
  trace_tipc_node_reset_links()
    tipc_node_dump()
      l = n-&amp;gt;links[0].link
                                       tipc_node_write_lock()
                                       kfree(l)
                                       n-&amp;gt;links[0].link = NULL
                                       tipc_node_write_unlock()
      tipc_link_dump(l)&lt;/p&gt;
&lt;p&gt;tipc_link_dump() then dereferences the stale pointer. KASAN reported:&lt;/p&gt;
&lt;p&gt;BUG: KASAN: slab-use-after-free in tipc_link_dump
  Read of size 4 by task poc/115
  Call Trace:
   tipc_link_dump+0x10cb/0x16b0
   tipc_node_dump+0x4bb/0x740
   trace_event_raw_event_tipc_node_class+0x258/0x360
   tipc_node_reset_links+0x14d/0x1a0
   tipc_rcv+0x13f5/0x3030
   tipc_udp_recv+0x4e3/0x670
  Allocated by task 0:
   tipc_link_create+0x1e1/0x1020
   tipc_node_check_dest+0x7d2/0x11a0
   tipc_disc_rcv+0xdbf/0x1430
  Freed by task 89:
   kfree+0x131/0x3c0
   tipc_node_link_down+0x267/0x4b0
   tipc_node_delete_links+0xec/0x160
   bearer_disable+0x107/0x260&lt;/p&gt;
&lt;p&gt;Take the node write lock around the trace event. This serializes the
dump ag…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-qwfh-hpch-ph73</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-99246</title>
      <link>https://db.gcve.eu/vuln/ubuntu-cve-2026-99246</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:Pro:18.04:LTS: linux-aws-5.4, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:Pro:18.04:LTS: linux-azure-5.4, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3 and 220 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: tipc: protect node reset trace dump with node lock The tipc_node_reset_links trace event asks tipc_node_dump() to walk the node&amp;#39;s link entries. Unlike the other node events that request link data, this event runs without the node lock. This permits bearer teardown to free a link while the trace callback is dumping it:   CPU 0                                CPU 1   trace_tipc_node_reset_links()     tipc_node_dump()       l = n-&amp;gt;links[0].link                                        tipc_node_write_lock()                                        kfree(l)                                        n-&amp;gt;links[0].link = NULL                                        tipc_node_write_unlock()       tipc_link_dump(l) tipc_link_dump() then dereferences the stale pointer. KASAN reported:   BUG: KASAN: slab-use-after-free in tipc_link_dump   Read of size 4 by task poc/115   Call Trace:    tipc_link_dump+0x10cb/0x16b0    tipc_node_dump+0x4bb/0x740    trace_event_raw_event_tipc_node_class+0x258/0x360    tipc_node_reset_links+0x14d/0x1a0    tipc_rcv+0x13f5/0x3030    tipc_udp_recv+0x4e3/0x670   Allocated by task 0:    tipc_link_create+0x1e1/0x1020    tipc_node_check_dest+0x7d2/0x11a0    tipc_disc_rcv+0xdbf/0x1430   Freed by task 89:    kfree+0x131/0x3c0    tipc_node_link_down+0x267/0x4b0    tipc_node_delete_links+0xec/0x160    bearer_disable+0x107/0x260 Take the node write lock around the trace event. This serializes the dump against t…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:Pro:18.04:LTS: linux-aws-5.4, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:Pro:18.04:LTS: linux-azure-5.4, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3 and 220 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: tipc: protect node reset trace dump with node lock The tipc_node_reset_links trace event asks tipc_node_dump() to walk the node&amp;#39;s link entries. Unlike the other node events that request link data, this event runs without the node lock. This permits bearer teardown to free a link while the trace callback is dumping it:   CPU 0                                CPU 1   trace_tipc_node_reset_links()     tipc_node_dump()       l = n-&amp;gt;links[0].link                                        tipc_node_write_lock()                                        kfree(l)                                        n-&amp;gt;links[0].link = NULL                                        tipc_node_write_unlock()       tipc_link_dump(l) tipc_link_dump() then dereferences the stale pointer. KASAN reported:   BUG: KASAN: slab-use-after-free in tipc_link_dump   Read of size 4 by task poc/115   Call Trace:    tipc_link_dump+0x10cb/0x16b0    tipc_node_dump+0x4bb/0x740    trace_event_raw_event_tipc_node_class+0x258/0x360    tipc_node_reset_links+0x14d/0x1a0    tipc_rcv+0x13f5/0x3030    tipc_udp_recv+0x4e3/0x670   Allocated by task 0:    tipc_link_create+0x1e1/0x1020    tipc_node_check_dest+0x7d2/0x11a0    tipc_disc_rcv+0xdbf/0x1430   Freed by task 89:    kfree+0x131/0x3c0    tipc_node_link_down+0x267/0x4b0    tipc_node_delete_links+0xec/0x160    bearer_disable+0x107/0x260 Take the node write lock around the trace event. This serializes the dump against t…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ubuntu-cve-2026-99246</guid>
    </item>
  </channel>
</rss>
