linux-kernel - Re: [PATCH v2] platform/chrome: cros_ec_dev

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAMHSBOVS-HDsixaEmjP_tYC55qFjU2+mB7bpoLoq2RT+zRNm8A@mail.gmail.com>
Date:	Tue, 8 Mar 2016 09:02:51 -0800
From:	Gwendal Grignou <gwendal@...omium.org>
To:	Olof Johansson <olof@...om.net>
Cc:	Gwendal Grignou <gwendal@...omium.org>, rdunlap@...radead.org,
	Olof Johansson <olofj@...omium.org>,
	Alan Cox <alan@...rguk.ukuu.org.uk>, cernekee@...omium.org,
	Linux Kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2] platform/chrome: cros_ec_dev - Fix security issue

On Sun, Mar 6, 2016 at 12:11 PM, Olof Johansson <olof@...om.net> wrote:
> Hi,
>
...
>
> How about you introduce a reasonable max size for a transaction instead
> (256K?), and compare data_size with that? Might want to check with the EC folks
> what they expect larges transactions to be from their side, and go with
> a margin above that.
Make sense, patch coming.
>
>
> Also, in your commit message you should refer to the CVE this fixes.
AFAIK, no CVE for this bug.
>
>
> -Olof