All of lore.kernel.org
 help / color / mirror / Atom feed
From: Serge Hallyn <serge.hallyn@canonical.com>
To: "Robert Święcki" <robert@swiecki.net>
Cc: Eugene Teo <eugeneteo@kernel.sg>,
	linux-kernel@vger.kernel.org, security@kernel.org,
	kees@ubuntu.com, Tavis Ormandy <taviso@cmpxchg8b.com>,
	David Howells <dhowells@redhat.com>
Subject: Re: [Security] Fwd: Oops (bad memory deref) in slab_alloc() due to filp_cachep holding incorrect values
Date: Wed, 25 May 2011 10:28:17 -0500	[thread overview]
Message-ID: <20110525152817.GC3507@mail.hallyn.com> (raw)
In-Reply-To: <BANLkTi=Y_+UBWGb5Kj9ga_bC0Fm7DosGVw@mail.gmail.com>

Quoting Robert Święcki (robert@swiecki.net):
> >> Given that it doesn't seem to appear in 2.6.39-rc4, and judging by the
> >> names of functions involved, this change looks suspiciously related to
> >> this oops (even if it just made the keyctl problem visible)
> >> http://git.itanic.dy.fi/?p=linux-stable;a=commitdiff;h=47a150edc2ae734c0f4bf50aa19499e23b9a46f8
> >>
> >> >> #include <sys/stat.h>
> >> >> #include <sys/wait.h>
> >> >> #include <unistd.h>
> >> >> #include <sys/syscall.h>
> >> >> #include <linux/keyctl.h>
> >> >> #include <linux/sched.h>
> >> >>
> >> >> int TH1(void *dummy) {
> >> >>        syscall(__NR_keyctl, KEYCTL_SESSION_TO_PARENT);
> >
> > Thanks!
> >
> > Fooi, it looks like all users of cred_alloc_blank() may need to be
> > audited wrt commit 47a150edc2ae734c0f4bf50aa19499e23b9a46f8.
> >
> > Does this fix the bug you're seeing?
> 
> Yup, the kernel survives both the testcase and a short syscall fuzzing
> session. Thanks.

Thanks, Robert.

David, assuming this gets your ack, do you mind pushing this one forward?

thanks,
-serge

      reply	other threads:[~2011-05-25 15:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-23 14:48 Oops (bad memory deref) in slab_alloc() due to filp_cachep holding incorrect values Robert Święcki
     [not found] ` <BANLkTikey3L4doiHY=__=690TZNsXqRHUQ@mail.gmail.com>
     [not found]   ` <alpine.DEB.2.00.1105231133580.29047@router.home>
2011-05-23 18:28     ` Fwd: " Robert Święcki
2011-05-24 19:52       ` Robert Święcki
2011-05-25  8:28         ` [Security] " Eugene Teo
2011-05-25 13:26           ` Robert Święcki
2011-05-25 14:44             ` Serge Hallyn
2011-05-25 14:52               ` Serge Hallyn
2011-05-25 15:07               ` Robert Święcki
2011-05-25 15:28                 ` Serge Hallyn [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=20110525152817.GC3507@mail.hallyn.com \
    --to=serge.hallyn@canonical.com \
    --cc=dhowells@redhat.com \
    --cc=eugeneteo@kernel.sg \
    --cc=kees@ubuntu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robert@swiecki.net \
    --cc=security@kernel.org \
    --cc=taviso@cmpxchg8b.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.