diff options
| author | Nikita Popov <npv1310@gmail.com> | 2021-08-09 20:17:34 +0530 |
|---|---|---|
| committer | Siddhesh Poyarekar <siddhesh@sourceware.org> | 2021-08-09 20:17:34 +0530 |
| commit | b805aebd42364fe696e417808a700fdb9800c9e8 (patch) | |
| tree | 9c933c8dee81700749fa69dd0ceb31d33c6a30df /socket | |
| parent | 60b4dd25790342b40e8942e3a4115f511a6b6911 (diff) | |
| download | glibc-b805aebd42364fe696e417808a700fdb9800c9e8.tar glibc-b805aebd42364fe696e417808a700fdb9800c9e8.tar.gz glibc-b805aebd42364fe696e417808a700fdb9800c9e8.tar.bz2 glibc-b805aebd42364fe696e417808a700fdb9800c9e8.zip | |
librt: fix NULL pointer dereference (bug 28213)
Helper thread frees copied attribute on NOTIFY_REMOVED message
received from the OS kernel. Unfortunately, it fails to check whether
copied attribute actually exists (data.attr != NULL). This worked
earlier because free() checks passed pointer before actually
attempting to release corresponding memory. But
__pthread_attr_destroy assumes pointer is not NULL.
So passing NULL pointer to __pthread_attr_destroy will result in
segmentation fault. This scenario is possible if
notification->sigev_notify_attributes == NULL (which means default
thread attributes should be used).
Signed-off-by: Nikita Popov <npv1310@gmail.com>
Reviewed-by: Siddhesh Poyarekar <siddhesh@sourceware.org>
Diffstat (limited to 'socket')
0 files changed, 0 insertions, 0 deletions