Am-I-affected-by-Meltdown
Am-I-affected-by-Meltdown copied to clipboard
raphaelsc
Meltdown Exploit / Proof-of-concept / checks whether system is affected by Variant 3: rogue data cache load (CVE-2017-5754), a.k.a MELTDOWN.
``` (gdb) r Starting program: /home/user/Am-I-affected-by-Meltdown-master/meltdown-checker error in line: (null) A irq_stack_union Program received signal SIGABRT, Aborted. 0x00007ffff716b860 in raise () from /usr/lib/libc.so.6 ```
Hello, I get an "illegal hardware instruction" when running this on Debian 8. Linux *snip* 4.9.0-0.bpo.5-amd64 #1 SMP Debian 4.9.65-3+deb9u2~bpo8+1 (2017-01-05) x86_64 GNU/Linux Strace output: ```` $ strace ./meltdown-checker execve("./meltdown-checker",...
In ac2c4350a5669495e2e92f993b3897937ffec23e, if `meltdown-checker` reads all-zero values, it will print out a "match" to whatever the first all-zero symbol is, but then follow this up with **`so far so good`**....
My box runs a custom-built Gentoo hardened monolithic kernel with most GRSEC protections enabled (so root doesn't see /proc/kallsyms), but no SELinux or other MAC. It also does not have...
Tried to run it: ``` root@5b51e04d92df:/Am-I-affected-by-Meltdown# ./meltdown-checker Unable to find symbol sys_call_table in symbol map. Aborting...Aborted ``` Not sure what that means.
Hello, In xbegin and xend functions, this program uses some older i386 instructions. For a proper x64-based CPU, if there's an alternative implementation won't it be better to use them...
