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>] [day] [month] [year] [list]
Date:	Wed, 06 Jan 2010 03:20:35 +0300
From:	Eugene Kapun <abacabadabacaba@...il.com>
To:	linux-kernel@...r.kernel.org
Subject: Does tkill/tgkill leak info from kernel stack?

As I can see, tkill and tgkill syscalls call do_tkill (kernel/signal.c:2336).
This function doesn't clear info struct, so it would contain what was on kernel
stack previously. And because SI_TKILL < 0, precautions in copy_siginfo_to_user
(kernel/signal.c:2154) won't prevent this data from going to userspace. Is it a
bug?
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ