<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://db.gcve.eu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-11-20T21:30:26.081398+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@gcve.eu</email>
  </author>
  <link href="https://db.gcve.eu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://db.gcve.eu/vuln/fkie_cve-2026-99433</id>
    <title>fkie_cve-2026-99433</title>
    <updated>2026-11-20T21:30:26.084822+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>ocfs2/dlm: hold a lock reference across grant AST enqueue</p>
<p>A newly granted remote lock must remain alive until its grant AST is
queued.  dlmlock_master() publishes the lock on res-&gt;granted with its base
and queue references, then drops res-&gt;spinlock before calling
dlm_queue_ast().  The resource's reserved AST count does not retain the
lock itself.</p>
<p>This can fail when a peer dies with an immediately grantable CREATE
buffered on its socket.  O2NET's node-down callback flushes receive work
before DLM cleanup, but the flush only waits for work queued on entry.  A
data-ready callback that already selected the socket container can queue
new receive work after the flush advances its work color.  Socket shutdown
does not discard bytes already queued for TCP receive.</p>
<p>The late receive work and DLM node-down cleanup can interleave as
follows (the lock reference operations shown are before this fix):</p>
<p>Socket data-ready        Node-down thread         Receive worker
  -----------------        ----------------         --------------
  o2net_data_ready()
    select sc under
    callback read lock
                           o2net_disconnect_node()
                             queue shutdown
                             begin flush; new color
    queue sc_rx_work
    in the new color
    release callback lock
                             shutdown socket
                             flush returns…</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/fkie_cve-2026-99433"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/ghsa-j695-h6vj-gqhh</id>
    <title>GHSA-j695-h6vj-gqhh</title>
    <updated>2026-11-20T21:30:26.084928+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>ocfs2/dlm: hold a lock reference across grant AST enqueue</p>
<p>A newly granted remote lock must remain alive until its grant AST is
queued.  dlmlock_master() publishes the lock on res-&gt;granted with its base
and queue references, then drops res-&gt;spinlock before calling
dlm_queue_ast().  The resource's reserved AST count does not retain the
lock itself.</p>
<p>This can fail when a peer dies with an immediately grantable CREATE
buffered on its socket.  O2NET's node-down callback flushes receive work
before DLM cleanup, but the flush only waits for work queued on entry.  A
data-ready callback that already selected the socket container can queue
new receive work after the flush advances its work color.  Socket shutdown
does not discard bytes already queued for TCP receive.</p>
<p>The late receive work and DLM node-down cleanup can interleave as
follows (the lock reference operations shown are before this fix):</p>
<p>Socket data-ready        Node-down thread         Receive worker
  -----------------        ----------------         --------------
  o2net_data_ready()
    select sc under
    callback read lock
                           o2net_disconnect_node()
                             queue shutdown
                             begin flush; new color
    queue sc_rx_work
    in the new color
    release callback lock
                             shutdown socket
                             flush returns…</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/ghsa-j695-h6vj-gqhh"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/wid-sec-w-2026-4695</id>
    <title>WID-SEC-W-2026-4695 — Linux Kernel: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff</title>
    <updated>2026-11-20T21:30:26.084974+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>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</p>
      </div>
    </content>
    <link href="https://db.gcve.eu/vuln/wid-sec-w-2026-4695"/>
  </entry>
</feed>
