[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130227063129.GZ1722@dhcp-25-225.brq.redhat.com>
Date: Wed, 27 Feb 2013 07:31:30 +0100
From: Petr Matousek <pmatouse@...hat.com>
To: oss-security@...ts.openwall.com
Subject: Re: CVE request - Linux kernel: VFAT slab-based
buffer overflow
On Tue, Feb 26, 2013 at 09:03:46PM -0800, Greg KH wrote:
> On Tue, Feb 26, 2013 at 11:41:53PM -0500, Michael Gilbert wrote:
> > Anyway, on a more serious note, at some point, acceptance will look
> > something like a real kernel-sec team that does essentially what you
> > just did, but on a continual basis: reviewing most/all commits for
> > potential security concerns and forwarding them to oss-sec to increase
> > identification and awareness to be applied downstream.
>
> I will say flat out that this is an impossible task to accomplish.
>
> As proof of that, I suggest you do this for just one major kernel
> release cycle (2-3 months long).
>
> You do know the number of patches applied to the Linux kernel every
> hour, right?
>
> Would you have caught the patch that started this thread? I sure
> didn't, and I was the one who originally applied it to the kernel tree
> in the first place. Doing "root-cause" research for every patch is
> non-trivial, as I know you realize.
For starters, security@...nel.org submissions should be posted to
oss-security or any other security related public mailing list when the
patch is being committed.
--
Petr Matousek / Red Hat Security Response Team
Powered by blists - more mailing lists
Please check out the
Open Source Software Security Wiki, which is counterpart to this
mailing list.
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
