Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date: Thu, 6 Mar 2014 13:47:38 -0800
From: Greg KH <>
Subject: Re: Re: CVE Request: staging/cxt1e1/linux.c: Correct
 arbitrary memory write in c4_ioctl()

On Thu, Mar 06, 2014 at 03:27:20PM -0500, wrote:
> The scope of CVE doesn't exclude issues that exist only in software
> that's at a beta level or similar level. See for example "Attendees
> agreed that CVE should include problems in beta software, provided
> that the beta code was intended for public dissemination" in the
> post.
> The CVEs of interest to the community tend to be ones that are
> "common" -- in other words, they are present at multiple sites, and a
> CVE ID would actually be used (typically in multiple contexts) as the
> mechanism for naming and tracking the vulnerability.
> For the specific case of staging drivers, a relevant example is "this
> driver is enabled in the Debian 6.0 kernel" for:

Thanks a lot for this information, I'll remember it for next time.

> So, any background about the discovery would be helpful, e.g., is the
> driver enabled in a distribution, or is someone shipping a Linux-based
> appliance or device that relies on the driver. The full list is
> substantial -- seems
> relevant although that's a third-party presentation and not directly
> the primary source.

The driver was merged into the 2.6.35 kernel release, so odds are, lots
of distros are enabling it and shipping it.

Note that you need to have CAP_SYS_ADMIN rights in order to cause this
problem, I don't know if that matters in the CVE assignment or not.


greg k-h

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.