[SECURITY] cdrom: fix improper type cast causing info leak (CVE-2018-18710)#127
Open
Mifacopy wants to merge 1 commit intofacebookincubator:oculus-go-kernel-masterfrom
Open
[SECURITY] cdrom: fix improper type cast causing info leak (CVE-2018-18710)#127Mifacopy 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.
Fix CVE-2018-18710.
Upstream commit: e4f3aa2e1e67bb48dfbaaf1cad59013d5a5bc276
cdrom_ioctl_select_disc() performed a bounds check after casting the user-
controlled argument from unsigned long to int. The cast could invalidate the
check, allowing an out-of-range value to be used later and potentially leak
kernel memory (information disclosure). This issue is similar to
CVE-2018-16658 and CVE-2018-10940.
Reference: CVE-2018-18710