From: "Anthony G. Basile" <blueness@gentoo.org>
To: gentoo-hardened@lists.gentoo.org
Subject: [gentoo-hardened] Security notice regarding hardened-sources
Date: Thu, 16 Sep 2010 17:15:14 -0400 [thread overview]
Message-ID: <4C9288E2.5010709@gentoo.org> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi everyone,
All kernels before Sept 14 are vulnerable to the "IA32 Syscall Entry
Point Privilege Escalation" and "IA32 Emulation Stack Underflow". See
http://bugs.gentoo.org/show_bug.cgi?id=337645
http://bugs.gentoo.org/show_bug.cgi?id=337659
Also see
https://bugs.gentoo.org/show_bug.cgi?id=326885#c10
As a result, certain configurations of hardened-sources are also
vulnerable. As a work around until I get the fix into the tree and fast
track stabilization, keep the following in mind:
1) Whether hardened or not, if you don't have CONFIG_IA32_EMULATION, the
exploits fail.
2) If you hide kernel symbols in /proc/kallsyms, the proof-of-concept
code won't work. You can do that by either not enabling CONFIG_KALLSYMS
on non-hardened kernels, or just set CONFIG_GRKERNSEC_HIDESYM=y on
hardened.
(However, there may still be ways of making the exploit work even
without symbol info.)
3) On hardened systems, if you enable CONFIG_PAX_MEMORY_UDEREF=y, the
exploits fail even with access to symbol info. If possible, I would
also recommend enabling CONFIG_PAX_KERNEXEC=y.
- --
Anthony G. Basile, Ph.D.
Gentoo Developer
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.16 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAkySiOIACgkQl5yvQNBFVTUZzQCeMolKjTKql6/ShNRtYSH/K1DM
thUAmwTJOrYbB1wJ4A+FlPDu78tc55AT
=xfQc
-----END PGP SIGNATURE-----
next reply other threads:[~2010-09-16 21:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-16 21:15 Anthony G. Basile [this message]
2010-09-16 22:47 ` [gentoo-hardened] Re: Security notice regarding hardened-sources 7v5w7go9ub0o
2010-09-17 0:21 ` Anthony G. Basile
2010-09-17 16:40 ` "Tóth Attila"
2010-09-17 4:06 ` Magnus Granberg
2010-09-17 23:12 ` 7v5w7go9ub0o
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=4C9288E2.5010709@gentoo.org \
--to=blueness@gentoo.org \
--cc=gentoo-hardened@lists.gentoo.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