CWE-663: Use of a Non-reentrant Function in a Concurrent Context
Filter
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.
What the weakness is: CWE-663 at MITRE. All weaknesses
Related attack patterns (CAPEC): 1
- CAPEC-29 Leveraging Time-of-Check and Time-of-Use (TOCTOU) Race Conditions Likelihood: High · Severity: High
The attack patterns MITRE's CAPEC relates to CWE-663, as MITRE names them. Credits.
Ask an AI about CWE-663
Show the prompt
Explain CWE-663: Use of a Non-reentrant Function in a Concurrent Context and how to prevent and detect it in code. Use https://cwe.mitre.org/data/definitions/663.html and https://cve.bz/cve/cwe/663?via=ask-ai-copy for recent CVEs with this weakness. Cite the sources.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this weakness's id and public links.
- 7.0CVE-2026-26201EPSS 0.3%
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…