CVE-2021-33574
glibc: mq_notify does not handle separately allocated thread attributes
Severity
LowRed Hat Product Security
CVSS 3.1
Review impact separately from score.
Published · May 21, 2021
Updated · October 14, 2026
Description
The mq_notify function in the GNU C Library (aka glibc) 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.
Statement
In order to mount a minimal attack using this flaw, an attacker needs many pre-requisites to be able to even crash a program using this mq_notify bug:
- The program call to mq_notify needs to be controlled by the attacker
- The program must provide attributes to control creation of the notification thread in mq_notify
- The program must have the race condition where it may potentially destroy the notification thread attributes before the notification thread is created
- The program must set CPU affinity of the notification thread to actually cause the use-after-free dereference
There are no known applications that have all these pre-requisites.
CVSS score applicability
The CVSS score(s) listed for this vulnerability do not reflect the associated product's status, and are included for informational purposes to better understand the severity of this vulnerability.
Mitigation
No mitigation is specified in collected source.
CVSS / CWE
CVSS 3.1 · 5.9CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
CWE-416 · Use After Free