From: Joseph Qi <joseph.qi@linux.alibaba.com>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
x86@kernel.org, Nadav Amit <namit@vmware.com>,
"Peter Zijlstra (Intel)" <peterz@infradead.org>,
Ingo Molnar <mingo@kernel.org>,
Greg KH <gregkh@linuxfoundation.org>
Cc: Caspar Zhang <caspar@linux.alibaba.com>,
jiufei Xue <jiufei.xue@linux.alibaba.com>
Subject: [bug report][stable] kernel tried to execute NX-protected page - exploit attempt? (uid: 0)
Date: Wed, 5 Jun 2019 18:23:40 +0800 [thread overview]
Message-ID: <5817eaac-29cc-6331-af3b-b9d85a7c1cd7@linux.alibaba.com> (raw)
Hi,
I have encountered a kernel BUG when running ltp ftrace-stress-test
on 4.19.48.
[ 209.704855] LTP: starting ftrace-stress-test (ftrace_stress_test.sh 90)
[ 209.739412] Scheduler tracepoints stat_sleep, stat_iowait, stat_blocked and stat_runtime require the kernel parameter schedstats=enable or kernel.sched_schedstats=1
[ 212.054506] kernel tried to execute NX-protected page - exploit attempt? (uid: 0)
[ 212.055595] BUG: unable to handle kernel paging request at ffffffffc0349000
[ 212.056589] PGD d00c067 P4D d00c067 PUD d00e067 PMD 23673e067 PTE 800000023457f061
[ 212.057759] Oops: 0011 [#1] SMP PTI
[ 212.058303] CPU: 0 PID: 0 Comm: swapper/0 Kdump: loaded Not tainted 4.19.48 #112
After some investigation I have found that it is introduced by commit
8715ce033eb3 ("x86/modules: Avoid breaking W^X while loading modules"),
and then revert this commit the issue is gone.
I have also tested the same case on 5.2-rc3 as well as right at
upstream commit f2c65fb3221a ("x86/modules: Avoid breaking W^X while
loading modules"), which has been merged in 5.2-rc1, it doesn't
happen.
So I don't know why only stable has this issue while upstream doesn't.
Thanks,
Joseph
next reply other threads:[~2019-06-05 10:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-05 10:23 Joseph Qi [this message]
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
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=5817eaac-29cc-6331-af3b-b9d85a7c1cd7@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=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