In commit 8b4416d, the 1: jump label in __mempcpy_chk was accidentally moved. This resulted in failures of mempcpy on CPU without SSE2.
https://sourceware.org/ml/libc-alpha/2015-02/msg00191.html
commit 132a1328eccd20621b77f7810eebbeec0a1af187 Author: Evangelos Foutras <evangelos@foutrelis.com> Date: Tue Feb 10 03:22:58 2015 +0000 Fix __memcpy_chk on non-SSE2 CPUs
Additional reference: https://bugs.archlinux.org/task/43753
Commit 8b4416d83c79ba77b0669203741c712880a09ae4 (“i386: memcpy functions with SSE2 unaligned load/store”) happened during 2.21 development, so 2.20 and earlier are not affected. I'm leaning towards treating this as a security issue because it can introduce application crashes in unexpected ways. The references indicate that the system is still usable to some degree, unlike with other string function bugs.