public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "npv1310 at gmail dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug librt/28213] New: NULL pointer dereference due to CVE-2021-33574 fix Date: Mon, 09 Aug 2021 12:14:00 +0000 [thread overview] Message-ID: <bug-28213-131@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=28213 Bug ID: 28213 Summary: NULL pointer dereference due to CVE-2021-33574 fix Product: glibc Version: unspecified Status: UNCONFIRMED Severity: normal Priority: P2 Component: librt Assignee: unassigned at sourceware dot org Reporter: npv1310 at gmail dot com Target Milestone: --- Hello. While investigating the upstream fix of the recent CVE-2021-33574, i've found following problem: 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). Affected file: sysdeps/unix/sysv/linux/mq_notify.c Affected function: helper_thread Affected lineno: 137 -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2021-08-09 12:14 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-08-09 12:14 npv1310 at gmail dot com [this message] 2021-08-09 12:29 ` [Bug librt/28213] " npv1310 at gmail dot com 2021-08-09 14:53 ` siddhesh at sourceware dot org 2021-08-12 12:10 ` siddhesh at sourceware dot org 2021-08-18 3:50 ` sam at gentoo dot org 2021-08-18 3:50 ` sam at gentoo dot org 2021-08-23 2:47 ` [Bug librt/28213] NULL pointer dereference in mq_notify (CVE-2021-38604) siddhesh at sourceware dot org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-28213-131@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).