[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4B718A7A.7080201@redhat.com>
Date: Wed, 10 Feb 2010 00:16:58 +0800
From: Eugene Teo <eugene@...hat.com>
To: oss-security@...ts.openwall.com
CC: Mark J Cox <mjc@...hat.com>, Greg KH <greg@...ah.com>,
"Steven M. Christey" <coley@...us.mitre.org>
Subject: Re: CVE request - kernel: ima: fix null pointer dereference
On 02/10/2010 12:13 AM, Mark J Cox wrote:
>>> Do we need CVE numbers for issues that never showed up in a released
>>> kernel version? I don't see how this could affect anyone, unless they
>>> were foolish enough to ship a product on a non-released kernel :)
>>
>> You got a point there, but I requested this in order to keep track of
>> security issues that we might need to backport in our future kernels.
>
> It shouldn't get a CVE name. If someone at some point in the future
> ships a vulnerable version (by selective backporting, or similar) then
> it would get a name. Cheers, Mark
Thanks for clarifying.
Eugene
--
Eugene Teo / 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.
