bugtraq - exploiting overflowed kmalloc() memory?

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

Message-ID: <20040618135347.36c3a3f4.infamous41md@hotpop.com>
Date: Fri, 18 Jun 2004 13:53:47 -0400
From: infamous41md@...pop.com
To: bugtraq@...urityfocus.com
Subject: exploiting overflowed kmalloc() memory?

has anyone done any research on exploiting overflows with memory returned by kmalloc()?  after briefly looking at source, i see that internally it relies on the kmem_cache_alloc() functions.  i didn't see any sort of coalescing as with dlmalloc, so maybe it's not even possible?  anyone have any links/info about this?