linux-kernel - Re: [patch] x86, i387: fix ptrace leakage using init

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] [day] [month] [year] [list]

Message-ID: <20080304081320.GA5689@elte.hu>
Date:	Tue, 4 Mar 2008 09:13:20 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Suresh Siddha <suresh.b.siddha@...el.com>
Cc:	hpa@...or.com, tglx@...utronix.de, linux-kernel@...r.kernel.org,
	roland@...hat.com
Subject: Re: [patch] x86, i387: fix ptrace leakage using init_fpu()


* Suresh Siddha <suresh.b.siddha@...el.com> wrote:

> This bug is introduced by the recent i387 merge.
> 
> Current usage of unlazy_fpu() in ptrace specific routines is wrong. 
> unlazy_fpu() will not init fpu if the task never used math. So the 
> ptrace calls can expose the parent tasks FPU data in some cases.
> 
> Replace it with the init_fpu() which will init the math state, if the 
> task never used math before.

thanks Suresh, good catch! Applied to x86.git.

	Ingo
--
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/