CVE-2021-33574: The mq_notify function in the GNU C Library (aka glibc) versions 2.32 and 2.33 has a use-after-free.

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

• debian debian linux10.0
• fedoraproject fedora33
• fedoraproject fedora34
• gnu glibc2.32
• gnu glibc2.33
• netapp cloud backupall versions
• netapp e-series santricity os controller11.0 and later · up to 11.70.1 inclusive
• netapp h300e firmwareall versions
• netapp h300s firmwareall versions
• netapp h410s firmwareall versions
• netapp h500e firmwareall versions
• netapp h500s firmwareall versions
• netapp h700e firmwareall versions
• netapp h700s firmwareall versions
• netapp solidfire baseboard management controller firmwareall versions

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Other highest-scoring records for the same primary product.

• CVE-2023-4911Glibc: buffer overflow in ld.so leading to privilege escalationKEV
  80Now
• CVE-2015-0235Heap-based buffer overflow in the __nss_hostname_digits_dots function in glibc 2.2, and other 2.x versions before 2.18, allows context-depen
  68This week
• CVE-2015-7547Multiple stack-based buffer overflows in the (1) send_dg and (2) send_vc functions in the libresolv library in the GNU C Library (aka glibc
  60This week

Published before and after this one in the same product

• ← EarlierCVE-2021-27645Feb 24, 2021 · The nameserver caching daemon (nscd) in the GNU C Library (aka glibc or libc6) 2.29 through 2.33, when processing a request for netgroup loo
  10Monitor
• ← EarlierCVE-2020-27618Feb 26, 2021 · The iconv function in the GNU C Library (aka glibc or libc6) 2.32 and earlier, when processing invalid multi-byte input sequences in IBM1364
  22Monitor
• Later →CVE-2021-35942Jul 22, 2021 · The wordexp function in the GNU C Library (aka glibc) through 2.33 may crash or read arbitrary memory in parse_param (in posix/wordexp.c) wh
  37Monitor

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

1free(dev->buf);2/* ... another thread is still running ... */3process(dev->buf);

1lock(&dev->lock);2free(dev->buf);3dev->buf = NULL;4unlock(&dev->lock);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.