Fix CVE-2016-3713: KVM x86 MTRR/MSR handling out-of-bounds access#116
Open
Mifacopy wants to merge 1 commit intofacebookincubator:oculus-go-kernel-masterfrom
Open
Fix CVE-2016-3713: KVM x86 MTRR/MSR handling out-of-bounds access#116Mifacopy wants to merge 1 commit intofacebookincubator:oculus-go-kernel-masterfrom
Mifacopy wants to merge 1 commit intofacebookincubator:oculus-go-kernel-masterfrom
Conversation
meta-cla
bot
added
the
CLA Signed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Background
KVM x86 had an out-of-bounds read/write issue in its MTRR/MSR handling path (triggerable via guest MSR access), tracked as CVE-2016-3713.
Changes
Harden arch/x86/kvm MTRR/MSR related code to validate inputs and prevent out-of-bounds access when processing the affected MSR/MTRR state.
Security Impact
Prevents guest-triggerable out-of-bounds memory access in KVM, addressing CVE-2016-3713.
References
Upstream commit: 9842df62004f366b9fed2423e24df10542ee0dc5; CVE: CVE-2016-3713