From: Thomas Gleixner <tglx@linutronix.de>
To: Baozeng Ding <sploving1@gmail.com>
Cc: linux-kernel@vger.kernel.org,
Red Hat Product Security <secalert@redhat.com>
Subject: Re: kernel/irq: Null-ptr deref on handle_irq_event_percpu function
Date: Wed, 16 Mar 2016 16:35:34 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.11.1603161632050.3978@nanos> (raw)
In-Reply-To: <56e974ff.878b420a.91092.ffffda23@mx.google.com>
On Wed, 16 Mar 2016, Baozeng Ding wrote:
> +linux-kernel and irq maitainer.
>
> On Thu, Feb 25, 2016 at 04:16:10AM -0500, Red Hat Product Security wrote:
> > >
> > > I cannot produce the bug, but by taking a look at the
> > > code(irq/handle.c line176), it may
> > > casue a null pointer deref:
> > >
> > > http://lxr.free-electrons.com/source/kernel/irq/handle.c#L176
That's the upstream code which is different from what you are pasting.
> > > 174 retval |= res;
> > > 175 action = action->next;
> > > 176 } while (action); //when action is null, it will
> > > //cause a null pointer deref.
That lacks upstream commit 570540d507 or stable 4.4.y commit 827685a637
Thanks,
tglx
prev parent reply other threads:[~2016-03-16 15:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <RT-Ticket-392702@engineering.redhat.com>
[not found] ` <56cdb3b9.8d45620a.4e20d.ffffb6ef@mx.google.com>
[not found] ` <rt-4.0.13-17913-1456391770-1186.392702-5-0@engineering.redhat.com>
2016-03-16 15:00 ` kernel/irq: Null-ptr deref on handle_irq_event_percpu function Baozeng Ding
2016-03-16 15:35 ` Thomas Gleixner [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=alpine.DEB.2.11.1603161632050.3978@nanos \
--to=tglx@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=secalert@redhat.com \
--cc=sploving1@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox