|
|
| |
|
| |
kernel: syscall instruction induces guest panic
| Package(s): | kernel |
CVE #(s): | CVE-2012-0045
|
| Created: | January 16, 2012 |
Updated: | January 18, 2012 |
| Description: |
From the Red Hat bugzilla:
32bit guests will crash (and 64bit guests may behave in a
wrong way) for example by simply executing following
nasm-demo-application:
[bits 32]
global _start
SECTION .text
_start: syscall
The reason seems a missing "invalid opcode"-trap (int6) for the
syscall opcode "0f05", which is not available on Intel CPUs
within non-longmodes, as also on some AMD CPUs within legacy-mode.
(depending on CPU vendor, MSR_EFER and cpuid)
Because previous mentioned OSs may not engage corresponding
syscall target-registers (STAR, LSTAR, CSTAR), they remain
NULL and (non trapping) syscalls are leading to multiple
faults and finally crashes. |
| Alerts: |
|
( Log in to post comments)
|
|
|