Twitter | Pretraživanje | |
Vitaly Nikolenko
doesn't seem like ubuntu 4.4 LTS kernels want to pull the upstream patch. can still rip <-- 0 with syscall(__NR_clock_gettime, 10, 0)
Reply Retweet Označi sa "sviđa mi se" More
Vitaly Nikolenko 6. lis
Odgovor korisniku/ci @vnik5287
combine with P0 null-page mmap bypass on older kernels / AMD or no-smep systems and you got yourself an easy ret2usr exploit
Reply Retweet Označi sa "sviđa mi se"
Gustavo A. R. Silva 6. lis
Odgovor korisniku/ci @vnik5287
Do you see this in LTS 4.9?
Reply Retweet Označi sa "sviđa mi se"
Vitaly Nikolenko 6. lis
Odgovor korisniku/ci @embeddedgus
don't know any Ubuntu lts versions that use 4.9? Upstream is fixed, it's just Ubuntu being special
Reply Retweet Označi sa "sviđa mi se"
Ori Nimron 6. lis
Odgovor korisniku/ci @vnik5287
Hi, Any idea why it didn't work for me?
Reply Retweet Označi sa "sviđa mi se"
Vitaly Nikolenko 6. lis
Odgovor korisniku/ci @orinimron123
hahah looks like it got un-"patched" in recent kernels. your version has the patch applied. try something more recent.. mine was 4.4.0-161 from Aug this year
Reply Retweet Označi sa "sviđa mi se"
Kees Cook 7. lis
Odgovor korisniku/ci @vnik5287 @colinianking
This looks like a bad backport in Ubuntu's 4.4. The upstream v4.4 doesn't carry the speculation fix at all. When posix_clocks[] changed from registration to static, the now-redundant .clock_get check was removed. It shouldn't be for v4.4:
Reply Retweet Označi sa "sviđa mi se"
Tyler Hicks 8. lis
Odgovor korisniku/ci @kees_cook @vnik5287 @colinianking
We've now got a fix making its way into our kernels:
Reply Retweet Označi sa "sviđa mi se"