public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Shaun Colley <shaunige@yahoo.co.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: i2c device driver bugs
Date: Tue, 15 Jun 2004 09:36:44 -0700	[thread overview]
Message-ID: <20040615163644.GB14078@kroah.com> (raw)
In-Reply-To: <20040615163244.10651.qmail@web25103.mail.ukl.yahoo.com>

On Tue, Jun 15, 2004 at 05:32:44PM +0100, Shaun Colley wrote:
> Okay, thanks for the info greg.
> 
> > Yes, this was a security issue a year ago, but has
> > been fixed since
> > then.  Vendors have released kernels that fix this
> > issue for their 2.4
> > kernels.  If not, I suggest you contact your vendor.
> 
> What I meant by silent was, did the issue actually get
> mentioned in any of the distro vendor's advisories?

I did see it be mentioned in a few.  But it really isn't that big of a
problem, as all distros seemed to have their /dev/i2c* nodes set to:
	$ ls -l /dev/i2c*
	crw-------  1 root root 89, 0 Feb 23 13:02 /dev/i2c0
	crw-------  1 root root 89, 0 Feb 23 13:02 /dev/i2c-0
	crw-------  1 root root 89, 1 Feb 23 13:02 /dev/i2c1
	crw-------  1 root root 89, 1 Feb 23 13:02 /dev/i2c-1

Which prevents any normal user from exploiting this issue.

thanks,

greg k-h

  parent reply	other threads:[~2004-06-15 16:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-13 18:41 i2c device driver bugs Shaun Colley
2004-06-14 21:21 ` Greg KH
2004-06-15 15:39   ` Shaun Colley
2004-06-15 16:13     ` Greg KH
2004-06-15 16:33       ` Shaun Colley
     [not found]       ` <20040615163244.10651.qmail@web25103.mail.ukl.yahoo.com>
2004-06-15 16:36         ` Greg KH [this message]
2004-06-15 17:09           ` Shaun Colley
2004-06-17 23:56             ` Greg KH
  -- strict thread matches above, loose matches on Subject: below --
2004-06-13 10:31 Shaun Colley

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20040615163644.GB14078@kroah.com \
    --to=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shaunige@yahoo.co.uk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox