<?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>Fri, 20 Nov 2026 21:22:38 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-99691 — ocfs2/cluster: unlink socket containers before releasing resources</title>
      <link>https://db.gcve.eu/vuln/cve-2026-99691</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;ocfs2/cluster: unlink socket containers before releasing resources&lt;/p&gt;
&lt;p&gt;A socket container&amp;#39;s node and socket must remain alive while the
container is on sock_containers. The debugfs formatter reads sc_node
and sc_sock under o2net_debug_lock without taking their references, but
sc_kref_release() releases both before taking that lock to unlink the
container.&lt;/p&gt;
&lt;p&gt;With CONFIG_DEBUG_FS enabled, a synchronous sender can retain its last
socket-container reference after o2net_disconnect_node() has detached
the connection and flushed o2net_wq. The caller runs outside that
workqueue. After the sender removes its configfs dependency, node
removal can proceed without waiting for the sender&amp;#39;s final sc_put():&lt;/p&gt;
&lt;p&gt;Sender (final sc_put)    Configfs rmdir        Debugfs reader
  --------------------    --------------        --------------
  o2nm_undepend_item()
                          Drop node item refs
  o2nm_node_put()
    [node can be freed]
                                               sc_seq_show()
                                                 Lock debug lock
                                                 Read sc_node-&amp;gt;nd_name
                                                 Unlock debug lock
  sc_node = NULL
  o2net_debug_del_sc()&lt;/p&gt;
&lt;p&gt;The earlier socket release has a similar window. The container is
still selectable while its socket has been released and sc_sock has
not yet been cleared:&lt;/p&gt;
&lt;p&gt;Sender (final sc_put)…&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;ocfs2/cluster: unlink socket containers before releasing resources&lt;/p&gt;
&lt;p&gt;A socket container&amp;#39;s node and socket must remain alive while the
container is on sock_containers. The debugfs formatter reads sc_node
and sc_sock under o2net_debug_lock without taking their references, but
sc_kref_release() releases both before taking that lock to unlink the
container.&lt;/p&gt;
&lt;p&gt;With CONFIG_DEBUG_FS enabled, a synchronous sender can retain its last
socket-container reference after o2net_disconnect_node() has detached
the connection and flushed o2net_wq. The caller runs outside that
workqueue. After the sender removes its configfs dependency, node
removal can proceed without waiting for the sender&amp;#39;s final sc_put():&lt;/p&gt;
&lt;p&gt;Sender (final sc_put)    Configfs rmdir        Debugfs reader
  --------------------    --------------        --------------
  o2nm_undepend_item()
                          Drop node item refs
  o2nm_node_put()
    [node can be freed]
                                               sc_seq_show()
                                                 Lock debug lock
                                                 Read sc_node-&amp;gt;nd_name
                                                 Unlock debug lock
  sc_node = NULL
  o2net_debug_del_sc()&lt;/p&gt;
&lt;p&gt;The earlier socket release has a similar window. The container is
still selectable while its socket has been released and sc_sock has
not yet been cleared:&lt;/p&gt;
&lt;p&gt;Sender (final sc_put)…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-99691</guid>
    </item>
  </channel>
</rss>
