linux-kernel - [PATCH 5.15 0/2] KVM: x86: Fix for dirty logging emulated atomics

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]

Date: Thu,  4 Apr 2024 16:40:02 -0700
From: Sean Christopherson <seanjc@...gle.com>
To: stable@...r.kernel.org, Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc: kvm@...r.kernel.org, linux-kernel@...r.kernel.org, 
	Sean Christopherson <seanjc@...gle.com>, Paolo Bonzini <pbonzini@...hat.com>, 
	David Matlack <dmatlack@...gle.com>, Pasha Tatashin <tatashin@...gle.com>, 
	Michael Krebs <mkrebs@...gle.com>, Jim Mattson <jmattson@...gle.com>
Subject: [PATCH 5.15 0/2] KVM: x86: Fix for dirty logging emulated atomics

Two KVM x86 backports for 5.15.  Patch 2 is the primary motivation (fix
for potential guest data corruption after live migration).

Patch 1 is a (very) soft dependency to resolve a conflict.  It's not strictly
necessary (manually resolving the conflict wouldn't be difficult), but it
is a fix that has been in upstream for a long time.  The only reason I didn't
tag it for stable from the get-go is that the bug it fixes is very
theoretical.  At this point, the odds of the patch causing problems are
lower than the odds of me botching a manual backport.

Sean Christopherson (2):
  KVM: x86: Bail to userspace if emulation of atomic user access faults
  KVM: x86: Mark target gfn of emulated atomic instruction as dirty

 arch/x86/kvm/x86.c | 12 +++++++++++-
 1 file changed, 11 insertions(+), 1 deletion(-)

base-commit: 9465fef4ae351749f7068da8c78af4ca27e61928
-- 
2.44.0.478.gd926399ef9-goog