On 15.03.2012 14:50, Stefan Bader wrote:
> On 14.03.2012 23:18, Stefan Bader wrote:
>> 32bit guests will crash (and 64bit guests may behave in a wrong way) for
>> example by simply executing following nasm-demo-application: 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)
>
>> Problem got introduced in 2.6.32 (so Hardy is not affected) and recently
>> fixed in a 3.3-rc. For Precise a simple cherry-pick of the two patches
>> works. Previous releases require a increasing amount of tweaking.
>> Following this email are the patches for Lucid till Precise. Since KVM
>> virtualization is not an option for ARM and neither EC2, only the master
>> branches should require this. If I did not forget something.
>
>> Changes tested on 32bit hosts/32bit guest for all releases and
>> additionally on a 64bit host/32bit+64bit guest for Lucid.
>
>> -Stefan
>
> As Maverick is slowly phasing out (which I failed to realize), I kept this
> one back until we get an assessment about its importance. All other patches
> applied to the respective master-next branches.
>
> -Stefan
>
Upon further discussion on IRC, I also applied the Maverick master-next
changes to be decided about later.
- -Stefan
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
APPLIED (Maverick, too): CVE-2012-0045
