<?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>Mon, 09 Nov 2026 17:24:56 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-99053</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-99053</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;tipc: hold a reference to nodes found by link name&lt;/p&gt;
&lt;p&gt;tipc_node_find_by_name() returns a node after dropping its RCU read lock
without taking a reference.  The LINK_SET, LINK_GET and LINK_RESET_STATS
handlers then lock and access the node, racing with timer-driven cleanup of
a down peer.  Generic netlink serialization does not exclude the node
timer.&lt;/p&gt;
&lt;p&gt;The following interleaving can leave a handler using a freed node:&lt;/p&gt;
&lt;p&gt;CPU 0: find the node under RCU and release the node read lock
  CPU 1: tipc_node_timeout() clears the links and unlinks the down node
  CPU 1: drop the list and timer references, queuing tipc_node_free()
  CPU 0: leave the RCU read-side critical section
  CPU 1: complete the grace period and free the node
  CPU 0: acquire the node lock through the stale pointer&lt;/p&gt;
&lt;p&gt;LINK_SET also uses the node&amp;#39;s media address after releasing the node lock,
when passing queued packets to tipc_bearer_xmit().&lt;/p&gt;
&lt;p&gt;KASAN on v7.3-rc5 reported:&lt;/p&gt;
&lt;p&gt;BUG: KASAN: slab-use-after-free in _raw_read_lock_bh
  Write of size 4 at addr ffff88807e06f008 by task poc/92
  Call Trace:
   _raw_read_lock_bh                 kernel/locking/spinlock.c:287
   tipc_nl_node_set_link             net/tipc/node.c:2475
   genl_family_rcv_msg_doit          net/netlink/genetlink.c:1114
   genl_rcv_msg                      net/netlink/genetlink.c:1209
   netlink_rcv_skb                   net/netlink/af_netlink.c:2575&lt;/p&gt;
&lt;p&gt;Allocated by task 0:
   tipc_node…&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: hold a reference to nodes found by link name&lt;/p&gt;
&lt;p&gt;tipc_node_find_by_name() returns a node after dropping its RCU read lock
without taking a reference.  The LINK_SET, LINK_GET and LINK_RESET_STATS
handlers then lock and access the node, racing with timer-driven cleanup of
a down peer.  Generic netlink serialization does not exclude the node
timer.&lt;/p&gt;
&lt;p&gt;The following interleaving can leave a handler using a freed node:&lt;/p&gt;
&lt;p&gt;CPU 0: find the node under RCU and release the node read lock
  CPU 1: tipc_node_timeout() clears the links and unlinks the down node
  CPU 1: drop the list and timer references, queuing tipc_node_free()
  CPU 0: leave the RCU read-side critical section
  CPU 1: complete the grace period and free the node
  CPU 0: acquire the node lock through the stale pointer&lt;/p&gt;
&lt;p&gt;LINK_SET also uses the node&amp;#39;s media address after releasing the node lock,
when passing queued packets to tipc_bearer_xmit().&lt;/p&gt;
&lt;p&gt;KASAN on v7.3-rc5 reported:&lt;/p&gt;
&lt;p&gt;BUG: KASAN: slab-use-after-free in _raw_read_lock_bh
  Write of size 4 at addr ffff88807e06f008 by task poc/92
  Call Trace:
   _raw_read_lock_bh                 kernel/locking/spinlock.c:287
   tipc_nl_node_set_link             net/tipc/node.c:2475
   genl_family_rcv_msg_doit          net/netlink/genetlink.c:1114
   genl_rcv_msg                      net/netlink/genetlink.c:1209
   netlink_rcv_skb                   net/netlink/af_netlink.c:2575&lt;/p&gt;
&lt;p&gt;Allocated by task 0:
   tipc_node…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-99053</guid>
    </item>
    <item>
      <title>GHSA-j7x4-wphj-g9x9</title>
      <link>https://db.gcve.eu/vuln/ghsa-j7x4-wphj-g9x9</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;tipc: hold a reference to nodes found by link name&lt;/p&gt;
&lt;p&gt;tipc_node_find_by_name() returns a node after dropping its RCU read lock
without taking a reference.  The LINK_SET, LINK_GET and LINK_RESET_STATS
handlers then lock and access the node, racing with timer-driven cleanup of
a down peer.  Generic netlink serialization does not exclude the node
timer.&lt;/p&gt;
&lt;p&gt;The following interleaving can leave a handler using a freed node:&lt;/p&gt;
&lt;p&gt;CPU 0: find the node under RCU and release the node read lock
  CPU 1: tipc_node_timeout() clears the links and unlinks the down node
  CPU 1: drop the list and timer references, queuing tipc_node_free()
  CPU 0: leave the RCU read-side critical section
  CPU 1: complete the grace period and free the node
  CPU 0: acquire the node lock through the stale pointer&lt;/p&gt;
&lt;p&gt;LINK_SET also uses the node&amp;#39;s media address after releasing the node lock,
when passing queued packets to tipc_bearer_xmit().&lt;/p&gt;
&lt;p&gt;KASAN on v7.3-rc5 reported:&lt;/p&gt;
&lt;p&gt;BUG: KASAN: slab-use-after-free in _raw_read_lock_bh
  Write of size 4 at addr ffff88807e06f008 by task poc/92
  Call Trace:
   _raw_read_lock_bh                 kernel/locking/spinlock.c:287
   tipc_nl_node_set_link             net/tipc/node.c:2475
   genl_family_rcv_msg_doit          net/netlink/genetlink.c:1114
   genl_rcv_msg                      net/netlink/genetlink.c:1209
   netlink_rcv_skb                   net/netlink/af_netlink.c:2575&lt;/p&gt;
&lt;p&gt;Allocated by task 0:
   tipc_node…&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: hold a reference to nodes found by link name&lt;/p&gt;
&lt;p&gt;tipc_node_find_by_name() returns a node after dropping its RCU read lock
without taking a reference.  The LINK_SET, LINK_GET and LINK_RESET_STATS
handlers then lock and access the node, racing with timer-driven cleanup of
a down peer.  Generic netlink serialization does not exclude the node
timer.&lt;/p&gt;
&lt;p&gt;The following interleaving can leave a handler using a freed node:&lt;/p&gt;
&lt;p&gt;CPU 0: find the node under RCU and release the node read lock
  CPU 1: tipc_node_timeout() clears the links and unlinks the down node
  CPU 1: drop the list and timer references, queuing tipc_node_free()
  CPU 0: leave the RCU read-side critical section
  CPU 1: complete the grace period and free the node
  CPU 0: acquire the node lock through the stale pointer&lt;/p&gt;
&lt;p&gt;LINK_SET also uses the node&amp;#39;s media address after releasing the node lock,
when passing queued packets to tipc_bearer_xmit().&lt;/p&gt;
&lt;p&gt;KASAN on v7.3-rc5 reported:&lt;/p&gt;
&lt;p&gt;BUG: KASAN: slab-use-after-free in _raw_read_lock_bh
  Write of size 4 at addr ffff88807e06f008 by task poc/92
  Call Trace:
   _raw_read_lock_bh                 kernel/locking/spinlock.c:287
   tipc_nl_node_set_link             net/tipc/node.c:2475
   genl_family_rcv_msg_doit          net/netlink/genetlink.c:1114
   genl_rcv_msg                      net/netlink/genetlink.c:1209
   netlink_rcv_skb                   net/netlink/af_netlink.c:2575&lt;/p&gt;
&lt;p&gt;Allocated by task 0:
   tipc_node…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-j7x4-wphj-g9x9</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-99053 — tipc: hold a reference to nodes found by link name</title>
      <link>https://db.gcve.eu/vuln/msrc_cve-2026-99053</link>
      <description>msrc_CVE-2026-99053</description>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/msrc_cve-2026-99053</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-99053</title>
      <link>https://db.gcve.eu/vuln/ubuntu-cve-2026-99053</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 229 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: tipc: hold a reference to nodes found by link name tipc_node_find_by_name() returns a node after dropping its RCU read lock without taking a reference.  The LINK_SET, LINK_GET and LINK_RESET_STATS handlers then lock and access the node, racing with timer-driven cleanup of a down peer.  Generic netlink serialization does not exclude the node timer. The following interleaving can leave a handler using a freed node:   CPU 0: find the node under RCU and release the node read lock   CPU 1: tipc_node_timeout() clears the links and unlinks the down node   CPU 1: drop the list and timer references, queuing tipc_node_free()   CPU 0: leave the RCU read-side critical section   CPU 1: complete the grace period and free the node   CPU 0: acquire the node lock through the stale pointer LINK_SET also uses the node&amp;#39;s media address after releasing the node lock, when passing queued packets to tipc_bearer_xmit(). KASAN on v7.3-rc5 reported:   BUG: KASAN: slab-use-after-free in _raw_read_lock_bh   Write of size 4 at addr ffff88807e06f008 by task poc/92   Call Trace:    _raw_read_lock_bh                 kernel/locking/spinlock.c:287    tipc_nl_node_set_link             net/tipc/node.c:2475    genl_family_rcv_msg_doit          net/netlink/genetlink.c:1114    genl_rcv_msg                      net/netlink/genetlink.c:1209    netlink_rcv_skb                   net/netlink/af_netlink.c:2575   Allocated by task 0:    tipc_node_create…&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 229 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: tipc: hold a reference to nodes found by link name tipc_node_find_by_name() returns a node after dropping its RCU read lock without taking a reference.  The LINK_SET, LINK_GET and LINK_RESET_STATS handlers then lock and access the node, racing with timer-driven cleanup of a down peer.  Generic netlink serialization does not exclude the node timer. The following interleaving can leave a handler using a freed node:   CPU 0: find the node under RCU and release the node read lock   CPU 1: tipc_node_timeout() clears the links and unlinks the down node   CPU 1: drop the list and timer references, queuing tipc_node_free()   CPU 0: leave the RCU read-side critical section   CPU 1: complete the grace period and free the node   CPU 0: acquire the node lock through the stale pointer LINK_SET also uses the node&amp;#39;s media address after releasing the node lock, when passing queued packets to tipc_bearer_xmit(). KASAN on v7.3-rc5 reported:   BUG: KASAN: slab-use-after-free in _raw_read_lock_bh   Write of size 4 at addr ffff88807e06f008 by task poc/92   Call Trace:    _raw_read_lock_bh                 kernel/locking/spinlock.c:287    tipc_nl_node_set_link             net/tipc/node.c:2475    genl_family_rcv_msg_doit          net/netlink/genetlink.c:1114    genl_rcv_msg                      net/netlink/genetlink.c:1209    netlink_rcv_skb                   net/netlink/af_netlink.c:2575   Allocated by task 0:    tipc_node_create…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ubuntu-cve-2026-99053</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-4152 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://db.gcve.eu/vuln/wid-sec-w-2026-4152</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise einen Denial-of-Service-Angriff auszulösen, Daten zu manipulieren oder offenzulegen oder Sicherheitsmaßnahmen zu umgehen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise einen Denial-of-Service-Angriff auszulösen, Daten zu manipulieren oder offenzulegen oder Sicherheitsmaßnahmen zu umgehen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/wid-sec-w-2026-4152</guid>
    </item>
  </channel>
</rss>
