CVE-2026-40943
Race Condition in Oxia Causes Server Panic and Deadlock
Publication date: 2026-04-21
Last updated on: 2026-04-21
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| oxia | metadata_store | to 0.16.2 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-362 | The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability exists in Oxia, a metadata store and coordination system, in versions prior to 0.16.2. It is caused by a race condition between session heartbeat processing and session closure. Specifically, the heartbeat() method performs a blocking channel send while holding a mutex. When this operation coincides with concurrent close() calls, it can lead to either a deadlock if the channel buffer is full or a panic due to sending on a closed channel after a time-of-check-to-time-of-use (TOCTOU) gap in the KeepAlive mechanism.
This issue is fixed in version 0.16.2.
How can this vulnerability impact me? :
The vulnerability can cause the Oxia server to panic or deadlock during session management operations. This can lead to service interruptions or crashes, potentially affecting the availability and reliability of systems relying on Oxia for metadata storage and coordination.
What immediate steps should I take to mitigate this vulnerability?
The vulnerability is fixed in Oxia version 0.16.2. Immediate mitigation involves upgrading the Oxia metadata store and coordination system to version 0.16.2 or later.