The mq_notify function in the GNU C Library (aka glibc) versions 2.32 and 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.
The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.
Link | Tags |
---|---|
https://sourceware.org/bugzilla/show_bug.cgi?id=27896 | issue tracking exploit third party advisory |
https://sourceware.org/bugzilla/show_bug.cgi?id=27896#c1 | issue tracking |
https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/RBUUWUGXVILQXVWEOU7N42ICHPJNAEUP/ | vendor advisory |
https://security.netapp.com/advisory/ntap-20210629-0005/ | third party advisory |
https://security.gentoo.org/glsa/202107-07 | third party advisory vendor advisory |
https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/KJYYIMDDYOHTP2PORLABTOHYQYYREZDD/ | vendor advisory |
https://lists.debian.org/debian-lts-announce/2022/10/msg00021.html | third party advisory mailing list |