linux-kernel - Re: [slab corruption] BUG key

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 for Android: free password hash cracker in your pocket

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

Message-ID: <31147.1232224402@redhat.com>
Date:	Sat, 17 Jan 2009 20:33:22 +0000
From:	David Howells <dhowells@...hat.com>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	dhowells@...hat.com, linux-kernel@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>,
	"Rafael J. Wysocki" <rjw@...k.pl>,
	Pekka Enberg <penberg@...helsinki.fi>,
	Michael LeMay <mdlemay@...ch.ncsc.mil>,
	James Morris <jmorris@...ei.org>,
	Stephen Smalley <sds@...ho.nsa.gov>,
	Paul Moore <paul.moore@...com>, Eric Paris <eparis@...hat.com>
Subject: Re: [slab corruption] BUG key_jar: Poison overwritten

Ingo Molnar <mingo@...e.hu> wrote:

> The problem was not reproducible - i tried the same config once more and 
> it didnt produce the bug. (this system has no known hardware flukes)

Having thought about it some more, we can't necessarily pin the blame on the
key management code.  I think it more likely due to the previous owner of the
page as it's the guard poisoning that got corrupted, not the allocated key
struct.  The problem is we don't know who that was.  I wonder if it's
practical to store a recent history of page allocs and releases in a circular
buffer.

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