Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <28fa9c5e0811201826n2ff949d6l1e384a3b34a3b164@mail.gmail.com>
Date: Fri, 21 Nov 2008 10:26:26 +0800
From: "Eugene Teo" <eugeneteo@...nel.sg>
To: oss-security@...ts.openwall.com
Cc: "Steven M. Christey" <coley@...us.mitre.org>, 
	"Mauro Chehab" <mchehab@...hat.com>
Subject: Re: CVE request: kernel: V4L/DVB (9621): Avoid writing outside shadow.bytes[] array

Hi Steve,

On Fri, Nov 21, 2008 at 9:59 AM, Steven M. Christey
<coley@...us.mitre.org> wrote:
>
> On Wed, 19 Nov 2008, Eugene Teo wrote:
>
>> If the write operation fails, the device won't be able to decode audio
>> signals properly, so on further analysis, we probably don't need a CVE
>> name for this. Take note.
>
> Does this mean, roughly, that this write only occurs into a different
> portion of a larger contiguous buffer, so it affects audio processing
> (e.g. throwing an error) or parsing, but otherwise can't be used to affect
> other memory locations outside that buffer?

To be honest, I'm not entirely familiar with the bug. I have Cc'ed
Mauro who is the maintainer of the driver, and he should be able to
share with us more about it.

Mauro, can you explain to us the implications of not including the
"V4L/DVB (9621): Avoid writing outside shadow.bytes[] array" fix, and
if it has a security consequence?

Thanks, Eugene

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.