linux-kernel - Re: KASAN use-after-free not showing freed stacktrace?

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:	Fri, 29 Jul 2016 23:55:54 +0200
From:	Vegard Nossum <vegard.nossum@...cle.com>
To:	Dmitry Vyukov <dvyukov@...gle.com>
Cc:	kasan-dev <kasan-dev@...glegroups.com>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: KASAN use-after-free not showing freed stacktrace?

On 07/29/2016 11:27 PM, Dmitry Vyukov wrote:
> On Fri, Jul 29, 2016 at 10:17 PM, Vegard Nossum
> <vegard.nossum@...cle.com> wrote:
>> Hi again,
>>
>> I am seeing some KASAN use-after-free bugs now but there is no
>> stacktrace for where they were freed anymore:
[...]
>> That seems like a regression, maybe related to memory quarantine
>> for SLUB? Or is there something else going on?

 > Do you use SLAB or SLUB? Is CONFIG_STACKDEPOT enabled? Kernel revision?

CONFIG_SLUB_DEBUG=y
# CONFIG_SLAB is not set
CONFIG_SLUB=y
# CONFIG_SLOB is not set
CONFIG_SLAB_FREELIST_RANDOM=y
CONFIG_SLUB_CPU_PARTIAL=y
CONFIG_SLABINFO=y
# CONFIG_SLUB_DEBUG_ON is not set
# CONFIG_SLUB_STATS is not set
CONFIG_FAILSLAB=y

CONFIG_STACKDEPOT=y

git version c624c86615fb8aa61fa76ed8c935446d06c80e77


Vegard