The C Standard, 7.28.5.6 paragraph 2 [ISO/IEC 9899:2024], states that a thread shall not be joined once it was previously joined or detached.
The termination of the other thread synchronizes with the completion of the thrd_join function. The thread identified by thr shall not have been previously detached or joined with another thread.
Similarly, subclause 7.28.5.3 paragraph 2 [ISO/IEC 9899:2024], states that a thread shall not be detached once it was previously joined or detached.
The thrd_detach function tells the operating system to dispose of any resources allocated to the thread identified by thr when that thread terminates. The thread identified by thr shall not have been previously detached or joined with another thread.
Violating either of these subclauses results in undefined behavior.
Noncompliant Code Example
This noncompliant code example detaches a thread that is later joined.
#include <stddef.h> #include <threads.h> int thread_func(void *arg) { /* Do work */ thrd_detach(thrd_current()); return 0; } int main(void) { thrd_t t; if (thrd_success != thrd_create(&t, thread_func, NULL)) { /* Handle error */ return 0; } if (thrd_success != thrd_join(t, 0)) { /* Handle error */ return 0; } return 0; }
Compliant Solution
This compliant solution does not detach the thread. Its resources are released upon successfully joining with the main thread:
#include <stddef.h> #include <threads.h> int thread_func(void *arg) { /* Do work */ return 0; } int main(void) { thrd_t t; if (thrd_success != thrd_create(&t, thread_func, NULL)) { /* Handle error */ return 0; } if (thrd_success != thrd_join(t, 0)) { /* Handle error */ return 0; } return 0; }
Risk Assessment
Joining or detaching a previously joined or detached thread is undefined behavior.
Rule | Severity | Likelihood | Remediation Cost | Priority | Level |
---|---|---|---|---|---|
CON39-C | Low | Likely | Medium | P6 | L2 |
Automated Detection
Tool | Version | Checker | Description |
---|---|---|---|
Astrée | 24.04 | Supported, but no explicit checker | |
CodeSonar | 8.1p0 | CONCURRENCY.TNJ | Thread is not Joinable |
Cppcheck Premium | 24.9.0 | premium-cert-con39-c | Fully implemented |
Helix QAC | 2024.3 | C1776 | |
Parasoft C/C++test | 2023.1 | CERT_C-CON39-a | Do not join or detach a thread that was previously joined or detached |
Polyspace Bug Finder | R2024a | CERT C: Rule CON39-C | Checks for join or detach of a joined or detached thread (rule fully covered) |
Related Vulnerabilities
Search for vulnerabilities resulting from the violation of this rule on the CERT website.
Bibliography
[ISO/IEC 9899:2024] | Subclause 7.28.5.3, "The |
1 Comment
Robert Seacord
There seem to be alot of undefined behaviors in C11 dealing with threading that aren't explicitlly listed in Annex J:
The C Standard, subclause 7.26.5.6 [ISO/IEC 9899:2011], specifically states that a thread shall not be joined once it was previously joined or detached. Similarly, subclause 7.26.5.3 states that a thread shall not be detached once it was previously joined or detached.