linux-kernel - Re: [tip:x86/urgent] x86-64, modify_ldt: Ban 16-bit segments on 64-bit kernels

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <1397346568.13490.105824481.72FA2B8D@webmail.messagingengine.com>
Date:	Sun, 13 Apr 2014 01:49:28 +0200
From:	Alexander van Heukelum <heukelum@...tmail.fm>
To:	"H. Peter Anvin" <hpa@...or.com>,
	Andy Lutomirski <luto@...capital.net>,
	Brian Gerst <brgerst@...il.com>,
	Ingo Molnar <mingo@...nel.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Thomas Gleixner <tglx@...utronix.de>, stable@...per.es
Subject: Re: [tip:x86/urgent] x86-64,
 modify_ldt: Ban 16-bit segments on 64-bit kernels

On Sun, Apr 13, 2014, at 1:31, H. Peter Anvin wrote:
> >>> d. Trampoline in user space
> >>>
> >>> A return to the vdso with values set up in registers r8-r15 would enable
> >>> a trampoline in user space.  Unfortunately there is no way
> >>> to do a far JMP entirely with register state so this would require
> >>> touching user space memory, possibly in an unsafe manner.
> > 
> > d.2. trampoline in user space via long mode
> > 
> > Return from the kernel to a user space trampoline via long mode.
> > The kernel changes the stack frame just before executing the iret
> > instruction. (the CS and RIP slots are set to run the trampoline code,
> > where CS is a long mode segment.) The trampoline code in userspace
> > is set up to this single instruction: a far jump to the final CS:EIP
> > (compatibility mode).
> 
> This still requires user space memory that the kernel can write to.
> Long mode is actually exactly identical to what I was suggesting above,
> except that I would avoid using self-modifying code in favor of just
> parameterization using the high registers.

No self modifying code... The far jump must be in the indirect form
anyhow. The CS:EIP must be accessible from user mode, but not
necessarily from compatibility mode. So the trampoline (the jump)
and data (CS:EIP) can live pretty much anywhere in virtual memory.
But indeed, I see what you meant now.

Greetings,
   Alexander

> 
> 	-hpa
> 
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/