linux-kernel - Re: Questions about to dos in emulate.c

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <54B3EB1C.3020208@redhat.com>
Date:	Mon, 12 Jan 2015 16:41:16 +0100
From:	Paolo Bonzini <pbonzini@...hat.com>
To:	nick <xerofoify@...il.com>, gleb@...nel.org
CC:	x86@...nel.org, kvm@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: Questions about to dos in emulate.c



On 10/01/2015 05:14, nick wrote:
> Greetings Again Everyone,
> I have a few questions about fix mes in emulate.c. They are listed
> in numerical order below.
> 1. For  __emulate_int_real somebody stated we need limit checks. What
> checks are needed for my information.

These are written in the manual as

  IF stack not large enough for a 6-byte return information
     THEN #SS; FI;

> 2. Secondly,about the function, emulate_iret_real are what do you mean 
> by stack limit checks and if possible what parts of the stacks for either
> guest(s) or hosts we need to check.

Same here:

  IF top 6 bytes of stack are not within stack limits
     THEN #SS; FI;

Paolo

> In addition if you need help with other work, please don't feel free to
> contact me.
> Thanks and Regards,
> Nick 
> 
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/