| 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: Wed, 14 Mar 2012 12:25:43 +0100 From: Johan Hovold <jhovold@...il.com> To: Marcel Holtmann <marcel@...tmann.org>, "Gustavo F. Padovan" <padovan@...fusion.mobi> Cc: "David S. Miller" <davem@...emloft.net>, linux-bluetooth@...r.kernel.org, linux-kernel@...r.kernel.org, netdev@...r.kernel.org, David Herrmann <dh.herrmann@...glemail.com>, Greg KH <gregkh@...uxfoundation.org> Subject: Re: [PATCH 0/3] bluetooth: bug fixes for 3.3 Hi Marcel and Gustavo, On Fri, Mar 09, 2012 at 04:43:23PM +0100, Johan Hovold wrote: > This is a revised series which also contains a minimal fix to the memory leak > discovered by David Hermann upon which the first NULL-pointer-dereference fix > also depends. > > These patches need to get to Linus ASAP as the problems are present in 3.3-rc6 > as well as earlier kernels and thus should be backported to the stable trees as > well. Any chance to get these into 3.3? Otherwise, is it possible to rebase bluetooth-next on top of these so that Greg can get them into 3.3.1 (and the other stable trees) once bluetooth-next is merged? All three bugs can be used to crash any kernel with HCI-UART support and can probably be used for exploits as they are extremely easy to trigger reliably. Thanks, Johan -- 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