Issue metadata
Sign in to add a comment
|
CVE-2018-1000204 CrOS: Vulnerability reported in Linux kernel |
||||||||||||||||||||||
Issue descriptionVOMIT (go/vomit) has received an external vulnerability report for the Linux kernel. Advisory: CVE-2018-1000204 Details: http://vomit.googleplex.com/advisory?id=CVE/CVE-2018-1000204 CVSS severity score: 6.3/10.0 Description: ** DISPUTED ** Linux Kernel version 3.18 to 4.16 incorrectly handles an SG_IO ioctl on /dev/sg0 with dxfer_direction=SG_DXFER_FROM_DEV and an empty 6-byte cmdp. This may lead to copying up to 1000 kernel heap pages to the userspace. This has been fixed upstream in https://github.com/torvalds/linux/commit/a45b599ad808c3c982fdcdc12b0b8611c2f92824 already. The problem has limited scope, as users don't usually have permissions to access SCSI devices. On the other hand, e.g. the Nero user manual suggests doing `chmod o+r+w /dev/sg*` to make the devices accessible. NOTE: third parties dispute the relevance of this report, noting that the requirement for an attacker to have both the CAP_SYS_ADMIN and CAP_SYS_RAWIO capabilities makes it "virtually impossible to exploit." This bug was filed by http://go/vomit Please contact us at vomit-team@google.com if you need any assistance.
,
Aug 24
,
Aug 24
,
Aug 30
Update: CL is still in CQ. CQ failures preventing CL from getting in.
,
Sep 5
CL submitted at https://chromium-review.googlesource.com/c/chromiumos/third_party/kernel/+/1186962, marking as Fixed.
,
Sep 6
,
Dec 12
This bug has been closed for more than 14 weeks. Removing security view restrictions. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by zsm@chromium.org
, Aug 23Labels: Security_Severity-Medium Security_Impact-Stable Pri-2
Owner: zsm@chromium.org
Status: Assigned (was: Untriaged)
Upstream commit is a45b599a("scsi: sg: allocate with __GFP_ZERO in sg_build_indirect()"). This patch is present in v4.14, v4.4. This patch is present in 3.18.y so I'll pull it down to v3.18.