[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20160823.112406.549221808236512285.davem@davemloft.net>
Date: Tue, 23 Aug 2016 11:24:06 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: ben@...adent.org.uk
Cc: luis.henriques@...onical.com, avijitnsec@...eaurora.org,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: CVE-2014-9900 fix is not upstream
From: Ben Hutchings <ben@...adent.org.uk>
Date: Tue, 23 Aug 2016 18:35:27 +0100
> On Tue, 2016-08-23 at 09:40 -0700, David Miller wrote:
>> From: Luis Henriques <luis.henriques@...onical.com>
>> Date: Tue, 23 Aug 2016 14:41:07 +0100
>>
>> > Digging through some old CVEs I came across this one that doesn't
>> seem be
>> > in mainline. Was there a good reason for not being sent upstream?
>> Maybe it was
>> > rejected for some reason and I failed to find the discussion.
>>
>> Because the patch is completely bogus, and thus so is the CVE.
>>
>> The variable initializer clears out the entire structure.
>>
>> Until you can show compiler output from gcc that shows it not
>> initializing the structure I will not apply this patch because I know
>> that it faithfully does.
>
> On some versions and architectures. Can you guarantee that you will
> notice when an exception appears?
Again, show me the assembler output exhibiting the lack of
initialization, for this specific structure and situation.
That's all that I'm asking.
Powered by blists - more mailing lists