public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Marc-Christian Petersen <m.c.p@kernel.linux-systeme.com>
Cc: linux-kernel@vger.kernel.org, Linus Torvalds <torvalds@osdl.org>,
	Andrew Morton <akpm@osdl.org>
Subject: Re: [SECURITY] CAN-2004-0075 (was: Re: [SECURITY] CAN-2004-0109 isofs fix.)
Date: Wed, 14 Apr 2004 14:27:24 -0700	[thread overview]
Message-ID: <20040414212724.GA24809@kroah.com> (raw)
In-Reply-To: <200404142230.33553@WOLK>

On Wed, Apr 14, 2004 at 10:30:33PM +0200, Marc-Christian Petersen wrote:
> On Wednesday 14 April 2004 19:11, Dave Jones wrote:
> 
> Hi,
> 
> > Merged in 2.4, and various vendor kernels today..
> 
> Okay, now while we are at fixing security holes, is there any chance we 
> can _finally_ get the attached patch in?
> 
> The Vicam USB driver in all Linux Kernels 2.6 mainline does not use the 
> copy_from_user function when copying data from userspace to kernel space, 
> which crosses security boundaries and allows local users to cause a denial
> of service.
> 
> Already ACKed by Greg. Only complaint was inproper coding style which is done 
> with attached patch ;)

Eeek, I thought this one was already in the tree, very sorry about that.

I'm applying it now and will send it to Linus in a bit.

thanks for reminding me,

greg k-h

  parent reply	other threads:[~2004-04-14 21:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-14 17:11 [SECURITY] CAN-2004-0109 isofs fix Dave Jones
2004-04-14 20:30 ` [SECURITY] CAN-2004-0075 (was: Re: [SECURITY] CAN-2004-0109 isofs fix.) Marc-Christian Petersen
2004-04-14 20:47   ` Dave Jones
2004-04-14 21:34     ` Marc-Christian Petersen
2004-04-14 21:27   ` Greg KH [this message]
2004-04-14 21:34     ` Marc-Christian Petersen
2004-04-15 10:04     ` [SECURITY] CAN-2004-0075 Michal Schmidt
2004-04-14 23:35   ` [SECURITY] CAN-2004-0177 (was: Re: [SECURITY] CAN-2004-0075) Marc-Christian Petersen
2004-04-15 10:21     ` Stephen C. Tweedie

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=20040414212724.GA24809@kroah.com \
    --to=greg@kroah.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m.c.p@kernel.linux-systeme.com \
    --cc=torvalds@osdl.org \
    /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