From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andy Lutomirski Subject: Re: [PATCH v2 0/9] procfs: protect /proc//* files with file->f_cred Date: Tue, 01 Oct 2013 18:40:41 -0700 Message-ID: <524B7999.60806@amacapital.net> References: <1380659178-28605-1-git-send-email-tixxdz@opendz.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: "Eric W. Biederman" , Kees Cook , Al Viro , Andrew Morton , Linus Torvalds , Ingo Molnar , "Serge E. Hallyn" , Cyrill Gorcunov , David Rientjes , LKML , linux-fsdevel@vger.kernel.org, kernel-hardening@lists.openwall.com, tixxdz@gmail.com To: Djalal Harouni Return-path: In-Reply-To: <1380659178-28605-1-git-send-email-tixxdz@opendz.org> Sender: linux-kernel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On 10/01/2013 01:26 PM, Djalal Harouni wrote: > /proc//* entries varies at runtime, appropriate permission checks > need to happen during each system call. > > Currently some of these sensitive entries are protected by performing > the ptrace_may_access() check. However even with that the /proc file > descriptors can be passed to a more privileged process > (e.g. a suid-exec) which will pass the classic ptrace_may_access() > check. In general the ->open() call will be issued by an unprivileged > process while the ->read(),->write() calls by a more privileged one. > > Example of these files are: > /proc/*/syscall, /proc/*/stack etc. > > And any open(/proc/self/*) then suid-exec to read()/write() /proc/self/* > > > These files are protected during read() by the ptrace_may_access(), > however the file descriptor can be passed to a suid-exec which can be > used to read data and bypass ASLR. Of course this was discussed several > times on LKML. Can you elaborate on what it is that you're fixing? That is, can you give a concrete example of what process opens what file and passes the fd to what process? I'm having trouble following your description. --Andy