4 ms·
Everyone is focused on this removal of the null check by the compiler, but to me that's a red herring. The real bug is the fact that SELinux allows you to map
by modeless 17y ago
Everyone is focused on this removal of the null check by the compiler, but to me that's a red herring. The real bug is the fact that SELinux allows you to map memory to address 0! Fix that and this is much less serious.
- jpierce420 17y agoReally...and here we thought SElinux was supposed to be 'more secure'. I love linux, and could read through the kernel source all day long, its freakin' beautiful, and have utmost respect for its developers. But I can't help but laughing when someone finds a vulnerability in the code, because...well you know how those kernel guys are...:-)
- tedunangst 17y agoApparently that's a deliberate design decision to allow root to map 0, which is why the attack vector goes through pulseaudio. Now why I haven't seen anybody screaming "WTF is a setuid program loading and running arbitrary code for?" is still a mystery.