From: Joseph Qi <joseph.qi@linux.alibaba.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Nadav Amit <namit@vmware.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
the arch/x86 maintainers <x86@kernel.org>,
"Peter Zijlstra (Intel)" <peterz@infradead.org>,
Ingo Molnar <mingo@kernel.org>,
Caspar Zhang <caspar@linux.alibaba.com>,
jiufei Xue <jiufei.xue@linux.alibaba.com>,
Sasha Levin <sashal@kernel.org>
Subject: Re: [bug report][stable] kernel tried to execute NX-protected page - exploit attempt? (uid: 0)
Date: Mon, 10 Jun 2019 09:38:03 +0800 [thread overview]
Message-ID: <6331bba5-0c6b-289f-5cc7-7d6099f3e4b1@linux.alibaba.com> (raw)
In-Reply-To: <20190609145001.GA26365@kroah.com>
Confirmed the following 3 upstream commits can resolve this issue:
d2a68c4effd8 x86/ftrace: Do not call function graph from dynamic trampolines
3c0dab44e227 x86/ftrace: Set trampoline pages as executable
7298e24f9042 x86/kprobes: Set instruction page as executable
And they are all included in stable 4.19.49.
Thanks,
Joseph
On 19/6/9 22:50, Greg KH wrote:
> On Sun, Jun 09, 2019 at 09:10:45PM +0800, Joseph Qi wrote:
>> Hi Nadav,
>> Thanks for the comments.
>> I'll test the 3 patches in the mentioned thread.
>
> This should all be fixed in the latest release that happened today. If
> not, please let us know.
>
> thanks,
>
> greg k-h
>
prev parent reply other threads:[~2019-06-10 1:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-05 10:23 Joseph Qi
2019-06-07 10:24 ` Joseph Qi
2019-06-07 16:38 ` Nadav Amit
2019-06-09 13:10 ` Joseph Qi
2019-06-09 14:50 ` Greg KH
2019-06-10 1:38 ` Joseph Qi [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=6331bba5-0c6b-289f-5cc7-7d6099f3e4b1@linux.alibaba.com \
--to=joseph.qi@linux.alibaba.com \
--cc=caspar@linux.alibaba.com \
--cc=gregkh@linuxfoundation.org \
--cc=jiufei.xue@linux.alibaba.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namit@vmware.com \
--cc=peterz@infradead.org \
--cc=sashal@kernel.org \
--cc=x86@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
Powered by JetHome