From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1753208AbdLNOet (ORCPT <rfc822;w@1wt.eu>);
        Thu, 14 Dec 2017 09:34:49 -0500
Received: from mail-pf0-f175.google.com ([209.85.192.175]:41645 "EHLO
        mail-pf0-f175.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1753161AbdLNOeq (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Thu, 14 Dec 2017 09:34:46 -0500
X-Google-Smtp-Source: ACJfBouKCCLadiYZsi5hORe3mMIJPLq0IGsRKPlezVR5qPZmWnXbQLD3jF9r58g/CusB7upYPxJxtq078U/zZLrnx/s=
MIME-Version: 1.0
In-Reply-To: <alpine.DEB.2.20.1712141525300.4998@nanos>
References: <94eb2c18a77ce8d832055f2cf263@google.com> <CACVxJT-WEm8KbmSCmQ_EWMRVDcoBp0g-DJRg89CJzi5+sekymg@mail.gmail.com>
 <CACT4Y+aTcJq7hu+azvd37XD09F8-PAXz4hNgKqYzXFb_iZndKQ@mail.gmail.com>
 <CACT4Y+ZGPYH5spxW=R5jn7=JCCo-_nfWvQdQLW7iESO+Lpmf9A@mail.gmail.com>
 <CACVxJT9Q+-1xGkVmdz+e6869Few90E+D8fMQWeSpW=MA76_03A@mail.gmail.com>
 <alpine.DEB.2.20.1711301355450.1925@nanos> <CAGXu5j+92ZebfVQHKoH0M3OcrqUC++YFj8EYy=kW7iNaa4_aFQ@mail.gmail.com>
 <20171212083343.GG22935@kroah.com> <alpine.DEB.2.20.1712141525300.4998@nanos>
From: Dmitry Vyukov <dvyukov@google.com>
Date: Thu, 14 Dec 2017 15:34:24 +0100
Message-ID: <CACT4Y+Yu1csMLNa0P=RfEtWC+f0VbnX8Q8L63doWqRJU0c5KLA@mail.gmail.com>
Subject: Re: general protection fault in show_timer
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Greg KH <greg@kroah.com>, Kees Cook <keescook@chromium.org>,
        Alexey Dobriyan <adobriyan@gmail.com>, security@kernel.org,
        Akinobu Mita <akinobu.mita@gmail.com>,
        Andrew Morton <akpm@linux-foundation.org>,
        "Eric W. Biederman" <ebiederm@xmission.com>,
        Josh Poimboeuf <jpoimboe@redhat.com>,
        LKML <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@kernel.org>,
        syzkaller-bugs@googlegroups.com,
        Vegard Nossum <vegard.nossum@oracle.com>
Content-Type: text/plain; charset="UTF-8"
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Thu, Dec 14, 2017 at 3:26 PM, Thomas Gleixner <tglx@linutronix.de> wrote:
> On Tue, 12 Dec 2017, Greg KH wrote:
>
>> On Tue, Dec 05, 2017 at 11:58:07AM -0800, Kees Cook wrote:
>> > On Thu, Nov 30, 2017 at 4:57 AM, Thomas Gleixner <tglx@linutronix.de> wrote:
>> > > On Thu, 30 Nov 2017, Alexey Dobriyan wrote:
>> > >
>> > >> [cc security@]
>> > >> 100% oops with interrupts disabled by nobody
>> > >> or kernel memory read
>> > >> [nods]
>> > >> you named the bug already
>> > >>
>> > >> "notify" directly comes from userspace struct sigevent::sigev_notify
>> > >> without adult supervision.
>> > >>
>> > >> Reproducer is timer_create + read(/proc/self/timers)
>> > >
>> > > Bah. That's a really old one.
>> > >
>> > > Tentative fix below. That needs more though but looking at the existing
>> > > check there is only one valid combo with SIGEV_THREAD_ID.
>> > >
>> > > Thanks,
>> > >
>> > >         tglx
>> > >
>> > > 8<----------------
>> > > --- a/kernel/time/posix-timers.c
>> > > +++ b/kernel/time/posix-timers.c
>> > > @@ -434,6 +434,16 @@ static struct pid *good_sigevent(sigeven
>> > >  {
>> > >         struct task_struct *rtn = current->group_leader;
>> > >
>> > > +       switch (event->sigev_notify) {
>> > > +       case SIGEV_NONE:
>> > > +       case SIGEV_SIGNAL:
>> > > +       case SIGEV_SIGNAL | SIGEV_THREAD_ID:
>> > > +       case SIGEV_THREAD:
>> > > +               break;
>> > > +       default:
>> > > +               return NULL;
>> > > +       }
>> > > +
>> > >         if ((event->sigev_notify & SIGEV_THREAD_ID ) &&
>> > >                 (!(rtn = find_task_by_vpid(event->sigev_notify_thread_id)) ||
>> > >                  !same_thread_group(rtn, current) ||
>> >
>> > FWIW, this looks correct to me.
>>
>> Did this ever go anywhere?  I don't see it in Linus's tree yet...
>
> I learned yesterday that syzboz is understuffed and cannot test patches, so
> I need to find a minute to run the reproducer myself and verify that the
> patch is correct.

Hi Thomas,

Why do you say so? Have you tried to ask it to test?
https://github.com/google/syzkaller/blob/master/docs/syzbot.md#communication-with-syzbot
What happened?