[32528] in bugtraq

home help back first fref pref prev next nref lref last post

Re: [aadams@securityfocus.com: Linux Kernel <= 2.4.21 MXCSR Local DOS Exploitation]

daemon@ATHENA.MIT.EDU (Thilo Schulz)
Sat Nov 22 13:29:16 2003

From: Thilo Schulz <arny@ats.s.bawue.de>
Reply-To: arny@ats.s.bawue.de
To: bugtraq@securityfocus.com
Date: Fri, 21 Nov 2003 22:52:07 +0100
In-Reply-To: <20031121001057.GA26614@securityfocus.com>
MIME-Version: 1.0
Content-Type: Text/Plain;
  charset="iso-8859-1"
Content-Description: clearsigned data
Content-Disposition: inline
Message-Id: <200311212252.13985.arny@ats.s.bawue.de>
Content-Transfer-Encoding: 8bit

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Friday 21 November 2003 01:10, David Ahmad wrote:
> Starting with the P3, Intel processors included SSE support which amongst
> many other things added the MXCSR register to handle SSE status and
> control information (and various behavioral flags). MXCSR is a 32-bit
> register, the MSB 16-bits of which are reserved. Intel specifies that if
> these reserved bits are written to a general protection fault (#GP) will
> occur.

An interesting question is: does this problem apply to AMD Processors as well 
if /proc/cpuinfo has sse included in the cpuflags?
Anyone able to clear this issue up?

- -- 
 - Thilo Schulz

My public GnuPG key is available at http://home.bawue.de/~arny/public_key.asc
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQE/vokKZx4hBtWQhl4RAr5RAJ91NUJcUxE5+XQDCZC2HgQ9UloauACfU+EI
NkylHPZY/s6RuNViJOmvE5M=
=/ETc
-----END PGP SIGNATURE-----


home help back first fref pref prev next nref lref last post