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
| ||
|
Date: Tue, 28 Nov 2017 23:06:18 +0100 From: Stephan Müller <smueller@...onox.de> To: herbert@...dor.apana.org.au Cc: syzbot <bot+b6e703f648ebbbf57a4528d4314e0c2a5c893dc2@...kaller.appspotmail.com>, davem@...emloft.net, linux-crypto@...r.kernel.org, linux-kernel@...r.kernel.org, syzkaller-bugs@...glegroups.com Subject: Re: general protection fault in crypto_remove_spawns Am Montag, 27. November 2017, 19:56:46 CET schrieb syzbot: Hi Herbert, The issue seems to trigger a bug whose results we have seen before. When starting the reproducer and stopping it shortly thereafter, I see the numerous identical entries in /proc/crypto: name : cmac(des3_ede) driver : cmac(des3_ede-asm) module : kernel priority : 200 refcnt : 1 selftest : passed internal : no type : shash blocksize : 8 digestsize : 8 name : cmac(des3_ede) driver : cmac(des3_ede-asm) module : kernel priority : 200 refcnt : 1 selftest : passed internal : no type : shash blocksize : 8 digestsize : 8 name : cmac(des3_ede) driver : cmac(des3_ede-asm) module : kernel priority : 200 refcnt : 1 selftest : passed internal : no type : shash blocksize : 8 digestsize : 8 ... And this list keeps on growing without end: # ./repro # less /proc/crypto | wc 9559 26456 188754 # ./repro # less /proc/crypto | wc 11440 31586 226032 At one point in time I think the system simply has too many entries. Ciao Stephan
Powered by blists - more mailing lists