From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S265772AbUFORJh (ORCPT ); Tue, 15 Jun 2004 13:09:37 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S265774AbUFORJh (ORCPT ); Tue, 15 Jun 2004 13:09:37 -0400 Received: from web25103.mail.ukl.yahoo.com ([217.12.10.51]:40090 "HELO web25103.mail.ukl.yahoo.com") by vger.kernel.org with SMTP id S265772AbUFORJg (ORCPT ); Tue, 15 Jun 2004 13:09:36 -0400 Message-ID: <20040615170912.19700.qmail@web25103.mail.ukl.yahoo.com> Date: Tue, 15 Jun 2004 18:09:12 +0100 (BST) From: =?iso-8859-1?q?Shaun=20Colley?= Subject: Re: i2c device driver bugs To: linux-kernel@vger.kernel.org In-Reply-To: <20040615163644.GB14078@kroah.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7BIT Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Well, I can't see it mentioned anywhere, but perhaps you're right. Anyway, thanks for the info. Although this isn't so much of a big deal (because of the fixes and mitagating factor), I think they would be exploitable in certain conditions, maybe... Last word: please could you point me to where you saw an announcement for these bugs in a security advisory? Thank you for your time. Shaun. ___________________________________________________________ALL-NEW Yahoo! Messenger - sooooo many all-new ways to express yourself http://uk.messenger.yahoo.com