From: Borislav Petkov <bp-Gina5bIWoIWzQB+pC5nmwQ@public.gmane.org>
To: Matt Fleming
<matt-mF/unelCI9GS6iBeEJttW/XRex20P6io@public.gmane.org>,
Kees Cook <keescook-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
Cc: Kosuke Tatsukawa <tatsu-zZGIbrA41Td8UrSeD/g0lQ@public.gmane.org>,
Thomas Gleixner <tglx-hfZtesqFncYOwBW4kG4KsQ@public.gmane.org>,
Ingo Molnar <mingo-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
"H. Peter Anvin" <hpa-YMNOUZJC4hwAvxtiuMwx3w@public.gmane.org>,
"x86-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org"
<x86-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
"linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH 1/2] x86: Fix kernel panic when booting with XD disabled in uEFI firmware
Date: Tue, 8 Dec 2015 15:19:46 +0100 [thread overview]
Message-ID: <20151208141946.GD27180@pd.tnic> (raw)
In-Reply-To: <20151208122557.GA2518-mF/unelCI9GS6iBeEJttW/XRex20P6io@public.gmane.org>
On Tue, Dec 08, 2015 at 12:25:57PM +0000, Matt Fleming wrote:
> On Mon, 07 Dec, at 11:10:43PM, Kosuke Tatsukawa wrote:
> >
> > Thank you pointing that out.
> >
> > linux-4.4-rc3 booted without a problem on a real server even with XD
> > turned off by the firmware. I didn't notice this before because I was
The aforementioned patch reenables NX.
> Borislav, what do you think about stripping PAGE_NX from 'page_flags'
> in kernel_map_pages_in_pgd() if NX isn't supported, rather than
> returning EINVAL? At least that way EFI runtime services would still
> work.
I guess we can - I mean, I don't see what can go wrong more when
allowing the kernel to execute even NX UEFI regions. Maybe easier
generation of "gadgets" in the ROP sense ...
On a related node, I'm very sceptical of the existence of this "noexec"
chicken bit, if you ask me. It is a really bad idea, security-wise, to
disable NX. Is there even a valid use case to disable NX?
Because if not, I'd vote for removing that chicken bit or at least
taining the kernel with
add_taint(TAINT_USER_MORON, ... );
Kees, has this NX disabling practice come up in the past, per chance... ?
Thanks.
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
WARNING: multiple messages have this Message-ID (diff)
From: Borislav Petkov <bp@alien8.de>
To: Matt Fleming <matt@codeblueprint.co.uk>,
Kees Cook <keescook@chromium.org>
Cc: Kosuke Tatsukawa <tatsu@ab.jp.nec.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
"x86@kernel.org" <x86@kernel.org>,
"linux-efi@vger.kernel.org" <linux-efi@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] x86: Fix kernel panic when booting with XD disabled in uEFI firmware
Date: Tue, 8 Dec 2015 15:19:46 +0100 [thread overview]
Message-ID: <20151208141946.GD27180@pd.tnic> (raw)
In-Reply-To: <20151208122557.GA2518@codeblueprint.co.uk>
On Tue, Dec 08, 2015 at 12:25:57PM +0000, Matt Fleming wrote:
> On Mon, 07 Dec, at 11:10:43PM, Kosuke Tatsukawa wrote:
> >
> > Thank you pointing that out.
> >
> > linux-4.4-rc3 booted without a problem on a real server even with XD
> > turned off by the firmware. I didn't notice this before because I was
The aforementioned patch reenables NX.
> Borislav, what do you think about stripping PAGE_NX from 'page_flags'
> in kernel_map_pages_in_pgd() if NX isn't supported, rather than
> returning EINVAL? At least that way EFI runtime services would still
> work.
I guess we can - I mean, I don't see what can go wrong more when
allowing the kernel to execute even NX UEFI regions. Maybe easier
generation of "gadgets" in the ROP sense ...
On a related node, I'm very sceptical of the existence of this "noexec"
chicken bit, if you ask me. It is a really bad idea, security-wise, to
disable NX. Is there even a valid use case to disable NX?
Because if not, I'd vote for removing that chicken bit or at least
taining the kernel with
add_taint(TAINT_USER_MORON, ... );
Kees, has this NX disabling practice come up in the past, per chance... ?
Thanks.
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
next prev parent reply other threads:[~2015-12-08 14:19 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-03 23:58 [PATCH 1/2] x86: Fix kernel panic when booting with XD disabled in uEFI firmware Kosuke Tatsukawa
[not found] ` <17EC94B0A072C34B8DCF0D30AD16044A0288E2D7-9lrffkYxhwTt6d3pZDjeaEtBU8KWyXPq@public.gmane.org>
2015-12-04 16:40 ` Matt Fleming
2015-12-04 16:40 ` Matt Fleming
[not found] ` <20151204164057.GE2514-mF/unelCI9GS6iBeEJttW/XRex20P6io@public.gmane.org>
2015-12-07 23:10 ` Kosuke Tatsukawa
2015-12-07 23:10 ` Kosuke Tatsukawa
[not found] ` <17EC94B0A072C34B8DCF0D30AD16044A0288EFC7-9lrffkYxhwTt6d3pZDjeaEtBU8KWyXPq@public.gmane.org>
2015-12-08 12:25 ` Matt Fleming
2015-12-08 12:25 ` Matt Fleming
[not found] ` <20151208122557.GA2518-mF/unelCI9GS6iBeEJttW/XRex20P6io@public.gmane.org>
2015-12-08 14:19 ` Borislav Petkov [this message]
2015-12-08 14:19 ` Borislav Petkov
[not found] ` <20151208141946.GD27180-fF5Pk5pvG8Y@public.gmane.org>
2015-12-08 20:30 ` Kees Cook
2015-12-08 20:30 ` Kees Cook
[not found] ` <CAGXu5jKF3fVc5rsU=+jRcoBGB+ZkeHjF6mmSeJN0SoP-MpFGow-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-12-08 20:39 ` H. Peter Anvin
2015-12-08 20:39 ` H. Peter Anvin
2015-12-08 20:54 ` Borislav Petkov
[not found] ` <19122B57-8052-4A92-801E-03CC84E66F06-YMNOUZJC4hwAvxtiuMwx3w@public.gmane.org>
2015-12-15 0:07 ` Andy Lutomirski
2015-12-15 0:07 ` Andy Lutomirski
2015-12-08 20:56 ` Borislav Petkov
2015-12-08 20:56 ` Borislav Petkov
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=20151208141946.GD27180@pd.tnic \
--to=bp-gina5biwoiwzqb+pc5nmwq@public.gmane.org \
--cc=hpa-YMNOUZJC4hwAvxtiuMwx3w@public.gmane.org \
--cc=keescook-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org \
--cc=linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=matt-mF/unelCI9GS6iBeEJttW/XRex20P6io@public.gmane.org \
--cc=mingo-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=tatsu-zZGIbrA41Td8UrSeD/g0lQ@public.gmane.org \
--cc=tglx-hfZtesqFncYOwBW4kG4KsQ@public.gmane.org \
--cc=x86-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.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 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.