mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jann Horn <jann@thejh.net>
To: Joe Korty <joe.korty@ccur.com>
Cc: "stable@vger.kernel.org" <stable@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] fix mm_access bug in pagemap_read
Date: Wed, 3 Aug 2016 22:43:54 +0200	[thread overview]
Message-ID: <20160803204354.GA12989@pc.thejh.net> (raw)
In-Reply-To: <20160803185830.GA26952@zipoli.ccur.com>

[-- Attachment #1: Type: text/plain, Size: 2261 bytes --]

On Wed, Aug 03, 2016 at 02:58:30PM -0400, Joe Korty wrote:
> On Tue, Aug 02, 2016 at 05:40:48PM -0400, Jann Horn wrote:
> > On Tue, Aug 02, 2016 at 03:26:53PM -0400, Joe Korty wrote:
> > > Hi Jann,
> > > The following linux-4.1.y git commit, y > 17,
> > > 
> > >     Commit caaee6234d05a58c5b4d05e7bf766131b810a657
> > >     Author: Jann Horn <jann@thejh.net>
> > >     Date:   Wed Jan 20 15:00:04 2016 -0800
> > > 
> > >     ptrace: use fsuid, fsgid, effective creds for fs access checks
> > > 
> > > broke linux-4.1.y with the following oops, repeated forever.
> > 
> > >    [   81.122531] ------------[ cut here ]------------
> > >    [   81.127161] WARNING: CPU: 6 PID: 5553 at kernel/ptrace.c:248 __ptrace_may_access+0x18a/0x1a0()
> > >    [   81.135780] denying ptrace access check without PTRACE_MODE_*CREDS
> > 
> > (Nit: That's just a warning, not an oops - it blocks access, but
> > doesn't kill the calling process. But still not good, of course.)
> > 
> > 
> > > The problem is that the above git commit missed one mm_access call
> > > that needed converting.  In this patch, we convert PTRACE_MODE_READ
> > > to PTRACE_MODE_READ_FSCREDS as that seems more correct for pagemap_read
> > > than PTRACE_MODE_READ_REALCREDS.
> > 
> > Yup, PTRACE_MODE_READ_FSCREDS is appropriate here.
> > 
> > 
> > > There may be stable releases other than linux-4.1.y that need this fix.
> > > 
> > > Signed-off-by: Joe Korty <joe.korty@ccur.com>
> > > 
> > > Index: b/fs/proc/task_mmu.c
> > > ===================================================================
> > > --- a/fs/proc/task_mmu.c
> > > +++ b/fs/proc/task_mmu.c
> > > @@ -1257,7 +1257,7 @@ static ssize_t pagemap_read(struct file 
> > >  	if (!pm.buffer)
> > >  		goto out_task;
> > >  
> > > -	mm = mm_access(task, PTRACE_MODE_READ);
> > > +	mm = mm_access(task, PTRACE_MODE_READ_FSCREDS);
> > >  	ret = PTR_ERR(mm);
> > >  	if (!mm || IS_ERR(mm))
> > >  		goto out_free;
> > 
> 
> 
> Hi Jann,
> Greg may need an 'Acked-by' from you before he can apply this fix.

Ah, okay. Sure, you can add:

Acked-by: Jann Horn <jann@thejh.net>

> Greg, I just looked at the longterm and the 4.7 releases and it
> appears that only 4.1 and 3.18 need this fix.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

      parent reply	other threads:[~2016-08-03 21:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20160802192653.GA2953@zipoli.ccur.com>
2016-08-02 21:40 ` Jann Horn
     [not found]   ` <20160803185830.GA26952@zipoli.ccur.com>
2016-08-03 20:43     ` Jann Horn [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20160803204354.GA12989@pc.thejh.net \
    --to=jann@thejh.net \
    --cc=joe.korty@ccur.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®