This bug was actually introduced by glibc, description can be found here
https://stackoverflow.com/questions/35656696/explanation-of-memcpy-memmove-glibc-2-14-2-2-5
This was patched to link explicitly in the glibc to an earlier version of memcpy, in order to overcome this issue
The source of the patched changes can be found here: