linux-kernel - Re: iwlagn: memory corruption with WPA enterprise

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]

Date:	Mon, 5 Mar 2012 16:18:08 +0100
From:	Tomáš Janoušek <tomi@...i.cz>
To:	Stanislaw Gruszka <sgruszka@...hat.com>
Cc:	wwguy <wey-yi.w.guy@...el.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"linux-wireless@...r.kernel.org" <linux-wireless@...r.kernel.org>,
	Johannes Berg <johannes@...solutions.net>, security@...nel.org
Subject: Re: iwlagn: memory corruption with WPA enterprise

Hello,

On Mon, Mar 05, 2012 at 04:11:41PM +0100, Stanislaw Gruszka wrote:
> Perhaps bug was triggered because KVM 32-bit guest had CONFIG_CRYPTO_AES_NI_INTEL
> enabled ?

Nope. CONFIG_CRYPTO_AES_NI_INTEL is enabled only in the 64-bit host kernel.
Guest kernel version is 2.6.32-220.2.1.el6.i686 and there's no mention of
AES_NI_INTEL in its .config.

(And I do run a 32-bit userspace, perhaps if I had 64-bit userspace, the guest
would be safe. Or maybe not. I have no idea and no time to get a 64-bit
userspace. :-))

-- 
Tomáš Janoušek, a.k.a. Liskni_si, http://work.lisk.in/
--
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/