Defined in 10 files
Last patched
__pthread_mutex_s in debian/glibc was changed by 7 published CVE fixes between 2018 and 2026, in 10 distinct patches that added or removed 712 lines in total.
The name occurs in 10 files: nptl/pthread_mutex_trylock.c, nptl/pthread_mutex_lock.c, nptl/pthread_mutex_timedlock.c, nptl/pthread_mutex_unlock.c, sysdeps/unix/sysv/linux/s390/force-elision.h, sysdeps/unix/sysv/linux/powerpc/force-elision.h, sysdeps/unix/sysv/linux/x86/force-elision.h, sysdeps/s390/nptl/bits/struct_mutex.h, sysdeps/powerpc/nptl/bits/struct_mutex.h, sysdeps/x86/nptl/bits/struct_mutex.h.
debian/glibc has 23 CVEs with a located fix in total, so 30% of them touched this function.
Every published CVE whose fix changed __pthread_mutex_s, newest first, with the lines each fix touched.
CVE-2026-19499 · sysdeps/powerpc/nptl/bits/struct_mutex.h · line 35 · +1 −1
CVE-2026-19499 · sysdeps/s390/nptl/bits/struct_mutex.h · line 35 · +1 −1
CVE-2026-19499 · sysdeps/x86/nptl/bits/struct_mutex.h · line 35 · +1 −1
CVE-2026-18374 · sysdeps/powerpc/nptl/bits/struct_mutex.h · line 35 · +1 −1
CVE-2026-18374 · sysdeps/s390/nptl/bits/struct_mutex.h · line 35 · +1 −1
CVE-2026-18374 · sysdeps/x86/nptl/bits/struct_mutex.h · line 35 · +1 −1
CVE-2019-9169 · nptl/pthread_mutex_lock.c · lines 65–66 · +2 −0
CVE-2019-9169 · nptl/pthread_mutex_timedlock.c · lines 56–57 · +2 −0
CVE-2019-9169 · nptl/pthread_mutex_trylock.c · lines 39–40 · +2 −0
CVE-2019-9169 · nptl/pthread_mutex_unlock.c · lines 38–39 · +2 −0
CVE-2019-9169 · sysdeps/unix/sysv/linux/powerpc/force-elision.h · lines 21–61 · +40 −4
CVE-2019-9169 · sysdeps/unix/sysv/linux/s390/force-elision.h · lines 21–61 · +40 −4
CVE-2019-9169 · sysdeps/unix/sysv/linux/x86/force-elision.h · lines 21–61 · +40 −4
CVE-2019-7309 · nptl/pthread_mutex_lock.c · lines 65–66 · +2 −0
CVE-2019-7309 · nptl/pthread_mutex_timedlock.c · lines 56–57 · +2 −0
CVE-2019-7309 · nptl/pthread_mutex_trylock.c · lines 39–40 · +2 −0
CVE-2019-7309 · nptl/pthread_mutex_unlock.c · lines 38–39 · +2 −0
CVE-2019-7309 · sysdeps/unix/sysv/linux/powerpc/force-elision.h · lines 21–61 · +40 −4
CVE-2019-7309 · sysdeps/unix/sysv/linux/s390/force-elision.h · lines 21–61 · +40 −4
CVE-2019-7309 · sysdeps/unix/sysv/linux/x86/force-elision.h · lines 21–61 · +40 −4
CVE-2016-10739 · nptl/pthread_mutex_lock.c · lines 65–66 · +2 −0
CVE-2016-10739 · nptl/pthread_mutex_timedlock.c · lines 56–57 · +2 −0
CVE-2016-10739 · nptl/pthread_mutex_trylock.c · lines 39–40 · +2 −0
CVE-2016-10739 · nptl/pthread_mutex_unlock.c · lines 38–39 · +2 −0
CVE-2016-10739 · sysdeps/unix/sysv/linux/powerpc/force-elision.h · lines 21–61 · +40 −4
CVE-2016-10739 · sysdeps/unix/sysv/linux/s390/force-elision.h · lines 21–61 · +40 −4
CVE-2016-10739 · sysdeps/unix/sysv/linux/x86/force-elision.h · lines 21–61 · +40 −4
CVE-2019-6488 · nptl/pthread_mutex_lock.c · lines 65–66 · +2 −0
CVE-2019-6488 · nptl/pthread_mutex_timedlock.c · lines 56–57 · +2 −0
CVE-2019-6488 · nptl/pthread_mutex_trylock.c · lines 39–40 · +2 −0
CVE-2019-6488 · nptl/pthread_mutex_unlock.c · lines 38–39 · +2 −0
CVE-2019-6488 · sysdeps/unix/sysv/linux/powerpc/force-elision.h · lines 21–61 · +40 −4
CVE-2019-6488 · sysdeps/unix/sysv/linux/s390/force-elision.h · lines 21–61 · +40 −4
CVE-2019-6488 · sysdeps/unix/sysv/linux/x86/force-elision.h · lines 21–61 · +40 −4
CVE-2018-19591 · nptl/pthread_mutex_lock.c · lines 65–66 · +2 −0
CVE-2018-19591 · nptl/pthread_mutex_timedlock.c · lines 56–57 · +2 −0
CVE-2018-19591 · nptl/pthread_mutex_trylock.c · lines 39–40 · +2 −0
CVE-2018-19591 · nptl/pthread_mutex_unlock.c · lines 38–39 · +2 −0
CVE-2018-19591 · sysdeps/unix/sysv/linux/powerpc/force-elision.h · lines 21–61 · +40 −4
CVE-2018-19591 · sysdeps/unix/sysv/linux/s390/force-elision.h · lines 21–61 · +40 −4
CVE-2018-19591 · sysdeps/unix/sysv/linux/x86/force-elision.h · lines 21–61 · +40 −4
Get an alert when the next CVE fix lands in debian/glibc, with the patched functions.
Monitor glibc CVEsFunctions in the same files that CVE fixes also changed.
Functions in debian/glibc changed by the most CVE fixes.
Common questions about CVE fixes to __pthread_mutex_s.
Fix locations are computed by RadicalNotion.AI from the upstream patch diff of each CVE. CVE data is sourced from the CVE Program.
Get an alert when a new CVE lands in this repository, with the patched functions and AI-written remediation guidance.
