linux-kernel - [PATCH 0/5] KVM: x86: Fix KVM behavior that does not follow spec

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>] [thread-next>] [day] [month] [year] [list]

Message-Id: <1397777591-6147-1-git-send-email-namit@cs.technion.ac.il>
Date:	Fri, 18 Apr 2014 02:33:06 +0300
From:	Nadav Amit <namit@...technion.ac.il>
To:	gleb@...nel.org, pbonzini@...hat.com
Cc:	tglx@...utronix.de, mingo@...hat.com, hpa@...or.com,
	x86@...nel.org, kvm@...r.kernel.org, linux-kernel@...r.kernel.org,
	Nadav Amit <namit@...technion.ac.il>
Subject: [PATCH 0/5] KVM: x86: Fix KVM behavior that does not follow spec

This series of patches fix various scenarios in which KVM behavior does not
follow x86 specifications.  Each patch actually deals with a separate bug.
These bugs can cause the guest to get stuck (i.e., make no progress), encounter
spurious injected exceptions, or cause guest code to misbehave. As a result
guest OS can potentially fail.

Thanks for reviewing the patches.

Nadav Amit (5):
  KVM: x86: Fix wrong/stuck PMU when guest does not use PMI
  KVM: x86: Fix CR3 reserved bits
  KVM: x86: IN instruction emulation should ignore REP-prefix
  KVM: x86: RSI/RDI/RCX are zero-extended when affected by string ops
  KVM: x86: Processor mode may be determined incorrectly

 arch/x86/include/asm/kvm_host.h |    6 +-----
 arch/x86/kvm/emulate.c          |   11 ++++++-----
 arch/x86/kvm/pmu.c              |    7 +++++--
 arch/x86/kvm/x86.c              |   27 ++++++---------------------
 4 files changed, 18 insertions(+), 33 deletions(-)

-- 
1.7.10.4

--
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/