Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754139Ab3IZUn2 (ORCPT ); Thu, 26 Sep 2013 16:43:28 -0400 Received: from mail-oa0-f48.google.com ([209.85.219.48]:54812 "EHLO mail-oa0-f48.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752951Ab3IZUnZ (ORCPT ); Thu, 26 Sep 2013 16:43:25 -0400 MIME-Version: 1.0 In-Reply-To: <1380140085-29712-7-git-send-email-tixxdz@opendz.org> References: <1380140085-29712-1-git-send-email-tixxdz@opendz.org> <1380140085-29712-7-git-send-email-tixxdz@opendz.org> Date: Thu, 26 Sep 2013 15:43:24 -0500 X-Google-Sender-Auth: v00RCK3hvI1ANs-Mv9HZPdsTo0c Message-ID: Subject: Re: [PATCH 06/12] procfs: make /proc/*/stack 0400 From: Kees Cook To: Djalal Harouni Cc: "Eric W. Biederman" , Al Viro , Andrew Morton , Linus Torvalds , Ingo Molnar , "Serge E. Hallyn" , Cyrill Gorcunov , LKML , "linux-fsdevel@vger.kernel.org" , "kernel-hardening@lists.openwall.com" , tixxdz@gmail.com Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1436 Lines: 36 On Wed, Sep 25, 2013 at 3:14 PM, Djalal Harouni wrote: > The /proc/*/stack contains sensitive information and currently its mode > is 0444. Change this to 0400 so the VFS will be able to block > unprivileged processes to get file descriptors on arbitrary privileged > /proc/*/stack files. > > The /proc/*/stack is a /procfs ONE file that shares the same ->open() > file operation with other ONE files. Doing a ptrace_may_access() check > during open() might break userspace from accessing other ONE files > like /proc/*/stat and /proc/*/statm. > > Therfore make it 0400 for now, and improve its check during ->read() > in the next following patch. > > Cc: Kees Cook > Cc: Eric W. Biederman > Signed-off-by: Djalal Harouni While the rest of the series is being discussed, I think it would be nice to at least get this into the tree. Fixing this reduces which processes are exposed to ASLR leaks. The rest of the series closes the remaining holes. I would if it would be valuable adding a test for the identified leak conditions to some test suite? LTP perhaps? -Kees -- Kees Cook Chrome OS Security -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/