Bug 1658985 (CVE-2017-13168) - CVE-2017-13168 kernel: scsi: sg driver can improperly access userspace memory
Summary: CVE-2017-13168 kernel: scsi: sg driver can improperly access userspace memory
Keywords:
Status: CLOSED NOTABUG
Alias: CVE-2017-13168
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard: impact=none,public=20171206,reported=...
Depends On:
Blocks: 1658989
TreeView+ depends on / blocked
 
Reported: 2018-12-13 10:34 UTC by Andrej Nemec
Modified: 2019-06-08 23:46 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
It was found that SCSI driver in the Linux kernel can improperly access userspace memory outside the provided buffer. A local privileged attacker could potentially use this flaw to expose information from the kernel memory.
Clone Of:
Environment:
Last Closed: 2019-01-21 17:50:13 UTC


Attachments (Terms of Use)

Description Andrej Nemec 2018-12-13 10:34:46 UTC
It was found that SCSI driver in the Linux kernel can improperly access userspace memory outside the provided buffer. A local privileged attacker could potentially use this flaw to expose information from the kernel memory.

References:

https://lore.kernel.org/lkml/20180615152335.208202-1-jannh@google.com/T/#u

https://lwn.net/Articles/760406/

https://source.android.com/security/bulletin/pixel/2017-12-01

https://github.com/LineageOS/android_kernel_xiaomi_msm8996/commit/4e624aeb719ba0a13390f70b18f2388372614b94

An upstream patch:

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=26b5b874aff5659a7e26e5b1997e3df2c41fa7fd

Comment 2 Vladis Dronov 2019-01-21 17:50:13 UTC
Note:

It apperared that an attacker would have to be able to open and aceess /dev/sg* which in RHEL systems are by default allowed to a privileged user (real non-container root) and members of the "disk" group (empty by default). Therefore we assume this issue is a bug and not a security flaw.


Note You need to log in before you can comment on or make changes to this bug.