diff options
author | Carlos O'Donell <carlos@redhat.com> | 2017-01-28 19:13:34 -0500 |
---|---|---|
committer | Carlos O'Donell <carlos@redhat.com> | 2017-01-28 19:21:44 -0500 |
commit | f8bf15febcaf137bbec5a61101e88cd5a9d56ca8 (patch) | |
tree | 77e4625039c3eb70b5dad4e1a1dcbb30517f3e60 /locale/localename.c | |
parent | faf0e9c84119742dd9ebb79060faa22c52ae80a1 (diff) | |
download | glibc-f8bf15febcaf137bbec5a61101e88cd5a9d56ca8.tar.gz glibc-f8bf15febcaf137bbec5a61101e88cd5a9d56ca8.tar.xz glibc-f8bf15febcaf137bbec5a61101e88cd5a9d56ca8.zip |
Bug 20116: Fix use after free in pthread_create()
The commit documents the ownership rules around 'struct pthread' and when a thread can read or write to the descriptor. With those ownership rules in place it becomes obvious that pd->stopped_start should not be touched in several of the paths during thread startup, particularly so for detached threads. In the case of detached threads, between the time the thread is created by the OS kernel and the creating thread checks pd->stopped_start, the detached thread might have already exited and the memory for pd unmapped. As a regression test we add a simple test which exercises this exact case by quickly creating detached threads with large enough stacks to ensure the thread stack cache is bypassed and the stacks are unmapped. Before the fix the testcase segfaults, after the fix it works correctly and completes without issue. For a detailed discussion see: https://www.sourceware.org/ml/libc-alpha/2017-01/msg00505.html
Diffstat (limited to 'locale/localename.c')
0 files changed, 0 insertions, 0 deletions