public inbox for glibc-cvs@sourceware.org help / color / mirror / Atom feed
From: Dmitry Levin <ldv@sourceware.org> To: glibc-cvs@sourceware.org Subject: [glibc/release/2.32/master] NEWS: Move CVE-2021-33574 entry from 2.32 section to 2.32.1 Date: Fri, 7 Oct 2022 08:20:02 +0000 (GMT) [thread overview] Message-ID: <20221007082002.44CB0382F98E@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=32022774db16ae5e41a940e559f11eb74bb011bf commit 32022774db16ae5e41a940e559f11eb74bb011bf Author: Dmitry V. Levin <ldv@altlinux.org> Date: Tue Oct 4 08:00:00 2022 +0000 NEWS: Move CVE-2021-33574 entry from 2.32 section to 2.32.1 The fix was backported by commit ff75390ef59823193351ae77584c397c503b7b58 ("Use __pthread_attr_copy in mq_notify (bug 27896)") after glibc 2.32 release. Diff: --- NEWS | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/NEWS b/NEWS index 5f43794bf5..cf8c54f681 100644 --- a/NEWS +++ b/NEWS @@ -13,6 +13,10 @@ Security related changes: invoked with input containing redundant shift sequences in the IBM1364, IBM1371, IBM1388, IBM1390, or IBM1399 character sets. + CVE-2021-33574: The mq_notify function has a potential use-after-free + issue when using a notification type of SIGEV_THREAD and a thread + attribute with a non-default affinity mask. + The following bugs are resolved with this release: [20019] NULL pointer dereference in libc.so.6 IFUNC due to uninitialized GOT @@ -258,10 +262,6 @@ Security related changes: Dytrych of the Cisco Security Assessment and Penetration Team (See TALOS-2020-1019). - CVE-2021-33574: The mq_notify function has a potential use-after-free - issue when using a notification type of SIGEV_THREAD and a thread - attribute with a non-default affinity mask. - The following bugs are resolved with this release: [9809] localedata: ckb_IQ: new Kurdish Sorani locale
reply other threads:[~2022-10-07 8:20 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20221007082002.44CB0382F98E@sourceware.org \ --to=ldv@sourceware.org \ --cc=glibc-cvs@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).