public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "siddhesh at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug nptl/27896] mq_notify does not handle separately allocated thread attributes (CVE-2021-33574)
Date: Mon, 31 May 2021 06:42:58 +0000	[thread overview]
Message-ID: <bug-27896-131-LzIrKbBzMV@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27896-131@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=27896

--- Comment #1 from Siddhesh Poyarekar <siddhesh at sourceware dot org> ---
Sorry I missed this in my Mitre CVE report: the only use-after-free indirection
is through the extensions member of struct pthread_attr (see
sysdeps/nptl/internaltypes.h) and it got introduced in glibc-2.32.  As a
result, only glibc-2.32 and glibc-2.33 have a use-after-free.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2021-05-31  6:42 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-21  8:54 [Bug nptl/27896] New: mq_notify does not handle separately allocated thread attributes fweimer at redhat dot com
2021-05-21  9:52 ` [Bug nptl/27896] " siddhesh at sourceware dot org
2021-05-26  5:30 ` [Bug nptl/27896] mq_notify does not handle separately allocated thread attributes (CVE-2021-33574) siddhesh at sourceware dot org
2021-05-31  6:42 ` siddhesh at sourceware dot org [this message]
2021-05-31  7:24 ` siddhesh at sourceware dot org
2021-06-01 15:14 ` schwab@linux-m68k.org
2021-06-03  5:54 ` siddhesh at sourceware dot org
2021-06-04  3:56 ` liqingqing3 at huawei dot com
2021-06-04  4:19 ` siddhesh at sourceware dot org
2021-06-16 17:43 ` manojh3012 at gmail dot com
2021-06-16 18:18 ` fweimer at redhat dot com
2021-06-17  1:26 ` manojh3012 at gmail dot com
2021-06-17  2:00 ` liqingqing3 at huawei dot com
2021-06-17  2:02 ` liqingqing3 at huawei dot com
2021-08-01 15:54 ` andyliuliming at outlook dot com
2021-08-02  0:51 ` carlos at redhat dot com

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-27896-131-LzIrKbBzMV@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: link
Be 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).