New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 800704 link

Starred by 1 user
Status: WontFix
Owner:
groeck@chromium.org
Closed: Jan 2018
Cc:
wonderfly@google.com
█ sawlani@google.com
chromeos-kernel-security-bug-access@google.com
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug-Security



Sign in to add a comment

CVE-2017-17853 CrOS: Vulnerability reported in Linux kernel

Project Member Reported by vomit.go...@appspot.gserviceaccount.com, Jan 10 2018 
VOMIT (go/vomit) has received an external vulnerability report for the Linux kernel. 

Advisory: CVE-2017-17853
  Details: http://vomit.googleplex.com/advisory?id=CVE/CVE-2017-17853
  CVSS severity score: 7.2/10.0
  Description:

kernel/bpf/verifier.c in the Linux kernel through 4.14.8 allows local users to cause a denial of service (memory corruption) or possibly have unspecified other impact by leveraging incorrect BPF_RSH signed bounds calculations.



This bug was filed by http://go/vomit
Please contact us at vomit-team@google.com if you need any assistance.

Comment 1 by groeck@chromium.org, Jan 10 2018

Cc: wonderfly@google.com
Labels: M-65 Security_Severity-High Security_Impact-None Pri-2
Owner: groeck@chromium.org
Status: ExternalDependency (was: Untriaged)
Only systems with BPF_SYSCALL enabled are affected, which is not the case in Chrome OS. Plan is to wait for the patch to be available from upstream stable, then merge into chromeos-4.4 and chromeos-4.14 through the regular stable release merge.

Comment 2 by groeck@chromium.org, Jan 10 2018

Status: WontFix (was: ExternalDependency)
Upstream 4374f256ce8182019353c0c639bb8d0695b4c941 ("bpf/verifier: fix bounds calculation on BPF_RSH"). Already fixed in both chromeos-4.4 and chromeos-4.14.

Comment 3 by wonderfly@google.com, Jan 10 2018

Cc: sawlani@google.com

Comment 4 by groeck@chromium.org, Jan 11 2018 

Correction: Lakitu has BPF_SYSCALL enabled, and the fix is not in chromeos-4.4. However, the problem was introduced with commit b03c9f9fdc37 ("bpf/verifier: track signed and unsigned min/max values"), which is not in chromeos-4.4, and chromeos-4.4 is therefore not affected.
►

Sign in to add a comment