<?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://cve.radiocsirt.org</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>Sat, 10 Oct 2026 07:19:43 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-292447</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-292447</link>
      <description>EUVD-2026-292447</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-292447</guid>
    </item>
    <item>
      <title>fkie_cve-2026-40943</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-40943</link>
      <description>&lt;p&gt;Oxia is a metadata store and coordination system. Prior to 0.16.2, a race condition between session heartbeat processing and session closure can cause the server to panic with send on closed channel. The heartbeat() method uses a blocking channel send while holding a mutex, and under specific timing with concurrent close() calls, this can lead to either a deadlock (channel buffer full) or a panic (send on closed channel after TOCTOU gap in KeepAlive). This vulnerability is fixed in 0.16.2.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Oxia is a metadata store and coordination system. Prior to 0.16.2, a race condition between session heartbeat processing and session closure can cause the server to panic with send on closed channel. The heartbeat() method uses a blocking channel send while holding a mutex, and under specific timing with concurrent close() calls, this can lead to either a deadlock (channel buffer full) or a panic (send on closed channel after TOCTOU gap in KeepAlive). This vulnerability is fixed in 0.16.2.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-40943</guid>
    </item>
    <item>
      <title>GHSA-5gqc-qhrj-9xw8 — Oxia affected by server crash via race condition in session heartbeat handling</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-5gqc-qhrj-9xw8</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/oxia-db/oxia&lt;/p&gt;
&lt;p&gt;### Summary
A race condition between session heartbeat processing and session closure can cause the server to panic with `send on closed channel`. The `heartbeat()` method uses a blocking channel send while holding a mutex, and under specific timing with concurrent `close()` calls, this can lead to either a deadlock (channel buffer full) or a panic (send on closed channel after TOCTOU gap in `KeepAlive`).&lt;/p&gt;
&lt;p&gt;### Impact
A remote client can trigger a server crash by sending rapid `KeepAlive` requests while a session is expiring or being closed. This is a denial-of-service vulnerability that crashes the entire data server process.&lt;/p&gt;
&lt;p&gt;All versions are affected.&lt;/p&gt;
&lt;p&gt;### Details
In `oxiad/dataserver/controller/lead/session.go`, the `heartbeat()` method performs a blocking `s.heartbeatCh &amp;lt;- true` send. If the channel buffer is full (size 1), this blocks while holding the session mutex, preventing `close()` from acquiring the lock to close the channel — a deadlock.&lt;/p&gt;
&lt;p&gt;Additionally, in `session_manager.go`, `KeepAlive()` releases the session manager&amp;#39;s read lock before calling `heartbeat()`, creating a TOCTOU window where the session can be removed and closed between the lookup and the heartbeat call.&lt;/p&gt;
&lt;p&gt;### Patches
Fixed by changing `heartbeat()` to use a non-blocking `select` with a `default` case, and by holding the session manager read lock through the entire `KeepAlive()` operation.&lt;/p&gt;
&lt;p&gt;### Workarounds
No workaround available.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/oxia-db/oxia&lt;/p&gt;
&lt;p&gt;### Summary
A race condition between session heartbeat processing and session closure can cause the server to panic with `send on closed channel`. The `heartbeat()` method uses a blocking channel send while holding a mutex, and under specific timing with concurrent `close()` calls, this can lead to either a deadlock (channel buffer full) or a panic (send on closed channel after TOCTOU gap in `KeepAlive`).&lt;/p&gt;
&lt;p&gt;### Impact
A remote client can trigger a server crash by sending rapid `KeepAlive` requests while a session is expiring or being closed. This is a denial-of-service vulnerability that crashes the entire data server process.&lt;/p&gt;
&lt;p&gt;All versions are affected.&lt;/p&gt;
&lt;p&gt;### Details
In `oxiad/dataserver/controller/lead/session.go`, the `heartbeat()` method performs a blocking `s.heartbeatCh &amp;lt;- true` send. If the channel buffer is full (size 1), this blocks while holding the session mutex, preventing `close()` from acquiring the lock to close the channel — a deadlock.&lt;/p&gt;
&lt;p&gt;Additionally, in `session_manager.go`, `KeepAlive()` releases the session manager&amp;#39;s read lock before calling `heartbeat()`, creating a TOCTOU window where the session can be removed and closed between the lookup and the heartbeat call.&lt;/p&gt;
&lt;p&gt;### Patches
Fixed by changing `heartbeat()` to use a non-blocking `select` with a `default` case, and by holding the session manager read lock through the entire `KeepAlive()` operation.&lt;/p&gt;
&lt;p&gt;### Workarounds
No workaround available.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-5gqc-qhrj-9xw8</guid>
    </item>
  </channel>
</rss>
