GPU VulnDB

Database/Kernel, userspace & hypervisor

glibc 2.32/2.33: use-after-free in mq_notify of the caller's notification thread attributes

CVSS 9.8CVE-2021-33574Kernel, userspace & hypervisorcurated

Impact

mq_notify in glibc 2.32 and 2.33 may use the notification thread attributes object passed through its struct sigevent parameter after the caller has freed it. The documented consequence is a crash of the calling application, with other unspecified impact possible; nothing in the record demonstrates code execution. Exposure is limited to processes that actually use POSIX message queues with thread notification, which is uncommon in a GPU serving or training stack, so for most operators this is a stability item on two specific glibc releases rather than a security exposure. The NVD vector of network access with no privileges is not supported by the description - treat the realistic case as a local crash of one process.

Who can reach it

Local only in practice: requires a process on the host that calls mq_notify with SIGEV_THREAD and frees the attributes object, on glibc 2.32 or 2.33. glibc provides no remotely reachable entry point here.

What to do

Move off glibc 2.32/2.33 to a patched release or take the distribution backport (Debian LTS, Fedora, Gentoo GLSA 202107-07). Updating glibc requires restarting every process linked against it, so plan a drain and reboot of each node; given the thin real-world exposure this belongs in a routine maintenance window.

References

Related entries

All Kernel, userspace & hypervisor entries

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.