http://arstechnica.com/security/2016/02 ... ulnerable/
http://lwn.net/Articles/676008/
Does this affect RuneAudio? If so, what steps can users take to fix/mitigate on the Rune device?
Edit: looks like yes since
pacman -Q glibc
says glibc 2.22-3 and the lwn page says that the fix will be in upcoming 2.22-4