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  PHC 
Open Source and information security mailing list archives
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Sun, 26 Oct 2014 17:18:19 +0000
From:	Al Viro <>
To:	Andy Lutomirski <>
Cc:	Richard Weinberger <>,,
	Andrew Morton <>,
	Kees Cook <>,
	linux-arch <>,
	Ingo Molnar <>,
Subject: Re: [PATCH] all arches, signal: Move restart_block to struct

On Sun, Oct 26, 2014 at 10:02:16AM -0700, Andy Lutomirski wrote:
> If an attacker can cause a controlled kernel stack overflow,
> overwriting the restart block is a very juicy exploit target.
> Moving the restart block to struct task_struct prevents this type of
> exploit.

The hell it does.  In a _lot_ of cases current is current_thread_info()->task,
which makes your variant just as vulnerable, in addition to being (slightly)
more costly.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists