Accessing the stack or thread-local variables of a thread from another thread can cause invalid memory accesses because the execution of threads can be interwoven within the constraints of the synchronization model. As a result, the referenced stack frame or thread-local variable may not be valid when the other thread tries to access it. Regular shared variables should be protected by thread synchronization mechanisms. However, local variables should not be shared in the same fashion because the referenced stack frame's thread would have to stop executing, or some other way must be found to ensure that the referenced stack frame is still valid. See CON32-C. Prevent data races when accessing bit-fields from multiple threads for information on how to securely share nonautomatic and non-thread-local variables. See DCL30-C. Declare objects with appropriate storage durations for information on how to declare objects with appropriate storage durations when data is not being shared between threads. Note that this is a specific instance of CON34-C. Declare objects shared between threads with appropriate storage durations for POSIX threads.
It is important to note that local data can be used securely with threads when using other non-POSIX thread interfaces, so the programmer should not always copy data into nonlocal memory when sharing data with threads. For example, the
shared keyword in OpenMP can be used in combination with OpenMP's threading interface to share local memory without having to worry about whether local automatic variables remain valid. Furthermore, copying the shared data into dynamic memory may completely negate the performance benefits of multithreading.
Noncompliant Code Example (Automatic Storage)
createThread() function allocates an integer on the stack and passes a void pointer, spawning off a new thread,
childThread(). The order of thread execution is interleaved, so
val can reference an object outside of its lifetime, causing the child thread to access an invalid memory location.
The automatic storage noncompliant code example incorrectly prints 0 when compiled with GCC 4.1.2 with the
-lpthread flag on Linux.
Noncompliant Code Example (Thread-Local Storage)
This noncompliant code example is incorrect because
createThread() can finish running before
childThread() may not access a valid object:
This thread-local storage noncompliant code example incorrectly prints 0 when compiled with GCC 4.1.2 with the
-lpthread flag on Linux.
Compliant Solution (Allocated Storage)
Instead of passing the pointer to the stack of the parent thread, one solution is to allocate space on the heap, copying the data to dynamic memory. Because the lifetime of an object stored in dynamic memory lasts until it is freed, the child thread ensures that memory accesses are valid.
Compliant Solution (Static Storage)
Another solution is to store the data as a global static variable. Unlike local automatic variables, which are stored on the stack, static variables are stored in the data section of memory. Static variables last for the execution of the entire program, so a thread can safely access global static variables.
Compliant Solution (Automatic Storage)
Another solution is to ensure that local variables shared between threads are declared in the same or previous stack frame as a call to a thread synchronization mechanism, such as
pthread_join(). For example, in this compliant solution,
val is declared in
pthread_join() is called. Because the parent thread will wait until the child thread completes before continuing its execution, the child thread is guaranteed to access an object that is still within its lifetime.
Compliant Solution (Thread-Local Storage)
Another solution is to declare
val a thread-local variable combined with a call to a thread synchronization mechanism, such as
pthread_join(). Because the parent thread will wait until the child thread completes before continuing its execution, the child thread is guaranteed to access an object that is still within its lifetime.
Threads that reference the stack of other threads can potentially overwrite important information on the stack, such as function pointers and return addresses. However, it would be difficult for an attacker to exploit this code from this error alone. The compiler will not generate warnings if the programmer decides to give another thread access to one thread's local variables, so a programmer may not catch a potential error at compile time. The remediation cost for this error is high because analysis tools have difficulty diagnosing problems with concurrency and race conditions.
|C4926, C4927, C4928|
Declare objects shared between POSIX threads with appropriate storage durations
|Polyspace Bug Finder|
|CERT C: Rule POS50-C||Checks for automatic or thread local variable escaping from a POSIX thread (rule fully covered)|
|4926, 4927, 4928|