glibc: CVE-2021-33574: mq_notify does not handle separately allocated thread attributes

Debian Bug report logs - #989147
glibc: CVE-2021-33574: mq_notify does not handle separately allocated thread attributes

Reply or subscribe to this bug.

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Salvatore Bonaccorso <carnil@debian.org>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: glibc: CVE-2021-33574: mq_notify does not handle separately allocated thread attributes

Date: Wed, 26 May 2021 21:57:12 +0200

Source: glibc
Version: 2.31-12
Severity: important
Tags: security upstream
Forwarded: https://sourceware.org/bugzilla/show_bug.cgi?id=27896
X-Debbugs-Cc: carnil@debian.org, Debian Security Team <team@security.debian.org>

Hi,

The following vulnerability was published for glibc, basically purely
to track the upstream issue and fix once coming downstream.

CVE-2021-33574[0]:
| The mq_notify function in the GNU C Library (aka glibc) through 2.33
| has a use-after-free. It may use the notification thread attributes
| object (passed through its struct sigevent parameter) after it has
| been freed by the caller, leading to a denial of service (application
| crash) or possibly unspecified other impact.


If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2021-33574
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-33574
[1] https://sourceware.org/bugzilla/show_bug.cgi?id=27896

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Send a report that this bug log contains spam.