Skip to content
OpenAdvisories

Weakness (CWE)

CWE-663: Use of a Non-reentrant Function in a Concurrent Context

Base Draft

The product calls a non-reentrant function in a concurrent context in which a competing code sequence (e.g. thread or signal handler) may have an opportunity to call the same function or otherwise influence its state.

How to prevent it (3 mitigations)

  1. Implementation

    Use reentrant functions if available.

  2. Implementation

    Add synchronization to your non-reentrant function.

  3. Implementation

    In Java, use the ReentrantLock Class.

Source: MITRE CWE-663

All Critical High Medium Low Exploited only Public exploit

1 result · Feed

  • High 7.0
    CVE-2026-26201

    emp3r0r Affected by Concurrent Map Access DoS (panic/crash)

    emp3r0r is a C2 designed by Linux users for Linux environments. Prior to version 3.21.2, multiple shared maps are accessed without consistent synchronization across goroutines. Under concurrent activity, Go runtime can trigger `fatal error: concurrent map rea…

    jm33-m0 emp3r0r github.com/jm33-m0/emp3r0r/core Go