All CWEs
CWE-663
Use of a Non-reentrant Function in a Concurrent Context
BaseDraftSimple1 CVE
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.
Common consequences1
- IntegrityConfidentialityOtherModify MemoryRead MemoryModify Application DataRead Application DataAlter Execution Logic
Potential mitigations3
- Implementation
Use reentrant functions if available.
- Implementation
Add synchronization to your non-reentrant function.
- Implementation
In Java, use the ReentrantLock Class.
Relationships1
- ChildOfCWE-662
CVEs referencing this CWE1
| CVE | Description | Severity | EPSS | Flags | Modified |
|---|---|---|---|---|---|
| CVE-2026-26201 | 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 read and map write`, causing C2 process crash (availability loss). Version 3.21.2 fixes this issue. | HIGH7.5 | 0.29%p21 | 2026-06-17 |