Received: by 2002:a25:c205:0:0:0:0:0 with SMTP id s5csp5327748ybf; Wed, 4 Mar 2020 22:25:33 -0800 (PST) X-Google-Smtp-Source: ADFU+vuHSJpi52aDurFRtEa1+WVfFsER68NoxMsUEN7KAg8nVpwNot+8WqVsQJHElz/LPnjOHdsY X-Received: by 2002:aca:d885:: with SMTP id p127mr3945056oig.154.1583389532955; Wed, 04 Mar 2020 22:25:32 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1583389532; cv=none; d=google.com; s=arc-20160816; b=eOtQk7sZ/Prq+f0WxkijIxhcErd0tVMEcpUdj1qGHEH0yLQpmw0vLyv/BlepayRmNP 768mKbbJIBcqaqWAHQCSOOs8qbxV3spqrKN3trtSiUe6r/5jLBjIhHTXNCwVJOijoVms 0IksXjaMzL/ww/TO0jOujbQvXi/6qtqIoo30DBGWtzhbf0wGtUcMhBEwrEEaVbabYpzR cDekTEiNyTPK0Gofh6kOGgtZHFZMVe7ucONk0jz0aGClEuLM5cBNvi8hUhRrk2omVyOu LsvV5AaSmJ+F99odu9YKQZByLJWqe/CiwIJRLGKMtycrF4UxU+tCOVUdkVLqvmzH8LgY k9zw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject:dkim-signature; bh=onavTSj9a/P9cQTzAh/dyBQ46vlcFHueFUhjebvWmRQ=; b=vgCvX68FMqCT2AVinSVq5nk94duR6AaQLePDJqpW1UzSSjxI55tmd3BvX5HU9SeMLG 6TTQraE7syM1Qubp44jRZUhPjanTyHC7vPeVVfm01rh0nN5qml9dCeslrG0FMrsrs1YL ZHN1q4J4pgYgiI49zDcocAYu8f9f0m9zkBt33LzxpBz0lv0f95XXgBF9FpGukX7rHYYa xjJwiu0ZhmoIzjkzIP89mykwieoq/ICb2BILmYhq8PtyoYxHcc23RMGLTww3UgufmDaq welLRPrFK2cKsxek8VinM/cJYMmjRKWQaDADAw0dnwqLzoWgNb7Tcmpx8Jk0TEvbRxb7 Ld+Q== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=aWdkEMMh; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id o50si671695ota.145.2020.03.04.22.25.21; Wed, 04 Mar 2020 22:25:32 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=aWdkEMMh; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1725893AbgCEGYw (ORCPT + 99 others); Thu, 5 Mar 2020 01:24:52 -0500 Received: from us-smtp-delivery-1.mimecast.com ([205.139.110.120]:32933 "EHLO us-smtp-1.mimecast.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1725816AbgCEGYw (ORCPT ); Thu, 5 Mar 2020 01:24:52 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1583389491; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=onavTSj9a/P9cQTzAh/dyBQ46vlcFHueFUhjebvWmRQ=; b=aWdkEMMhEDBGMDKsL74iXqhXbmLnKR7IoxtQJ1KOZTyMum/0aKxm4IauRzXzrjr0pxP+kG mJ89rbQJcijimucAvUXLDODU+tEJ9YfQz/13C/q/NmGu2/8fGho/OCJqiiIj7tzbcQr9fl tiN93UYZygKbWbIP/E9gJ0Rc1fKfq6c= Received: from mail-wm1-f71.google.com (mail-wm1-f71.google.com [209.85.128.71]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-382-PWnfSI4RMoeXOtCKVl1Gsg-1; Thu, 05 Mar 2020 01:24:47 -0500 X-MC-Unique: PWnfSI4RMoeXOtCKVl1Gsg-1 Received: by mail-wm1-f71.google.com with SMTP id b23so1693874wmj.3 for ; Wed, 04 Mar 2020 22:24:47 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=onavTSj9a/P9cQTzAh/dyBQ46vlcFHueFUhjebvWmRQ=; b=WK/8zucVyHdyHYHB7fn2TEb1+1+qe4aoQDes5xPmNehWxp564hwmMUEfgx5EayZISG +KwbGR2ha4RfMNP0/eei+ytYsPTXN+cTjX6Z6fGVjnOxUjnzhusxsH+28AxZHutrHJpe wCXTRXTXxHm6Q78Fm3JyuiEluQT7sGvUlf7hKjThiUGvWHM9yqWCAPCBNqgvKO6f+/p8 ocmMtiPwzTp/Ir7jQisn6pb4hjxDxSyEyrIGmR6n2m5JidUDO+2CfBY5IJEq6dfoBaN9 ior28hjWM+aIqlSstPbLOjyydyFeD0F9+6+rpiILgPVjdgI1JMiocvWgXvPb7TjloxRL n+/g== X-Gm-Message-State: ANhLgQ3OIS2ToK3fVeBhEspCwpoUBe4Z3e7iFdTzfXrAcIGz3pDGM28w rHY4Yg1AwWJBrpgDUS3fJ3PjPzWF/LbGQuwyPpbmhIuUrYG/Q26imlgOklGH0ZnatTUjhPcyEpe 9vXR0+gTLa3UelYjmGy81ZBCY X-Received: by 2002:a1c:e91a:: with SMTP id q26mr7582620wmc.103.1583389485992; Wed, 04 Mar 2020 22:24:45 -0800 (PST) X-Received: by 2002:a1c:e91a:: with SMTP id q26mr7582593wmc.103.1583389485734; Wed, 04 Mar 2020 22:24:45 -0800 (PST) Received: from x1.localdomain (2001-1c00-0c0c-fe00-7a91-34f6-66f7-d87c.cable.dynamic.v6.ziggo.nl. [2001:1c00:c0c:fe00:7a91:34f6:66f7:d87c]) by smtp.gmail.com with ESMTPSA id p10sm39285099wrx.81.2020.03.04.22.24.44 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 04 Mar 2020 22:24:44 -0800 (PST) Subject: Re: Updating cypress/brcm firmware in linux-firmware for CVE-2019-15126 To: chi-hsien.lin@cypress.com, Christopher Rumpf , Chung-Hsien Hsu Cc: linux-firmware@kernel.org, Linux Kernel Mailing List References: <93dba8d2-6e46-9157-d292-4d93feb8ec1a@redhat.com> <3cf961a6-56c8-81fb-3bf9-fc36e2601d2c@cypress.com> From: Hans de Goede Message-ID: <17ec344e-80c5-02a9-59a3-35789a2eaaf9@redhat.com> Date: Thu, 5 Mar 2020 07:24:44 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.5.0 MIME-Version: 1.0 In-Reply-To: <3cf961a6-56c8-81fb-3bf9-fc36e2601d2c@cypress.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, On 3/5/20 4:50 AM, Chi-Hsien Lin wrote: > (+Chris) > > On 03/04/2020 7:45, Hans de Goede wrote: >> Hi, >> >> On 2/26/20 11:16 PM, Hans de Goede wrote: >>> Hello Cypress people, >>> >>> Can we please get updated firmware for >>> brcm/brcmfmac4356-pcie.bin and brcm/brcmfmac4356-sdio.bin >>> fixing CVE-2019-15126 as well as for any other affected >>> models (the 4356 is explicitly named in the CVE description) ? >>> >>> The current Cypress firmware files in linux-firmware are >>> quite old, e.g. for brcm/brcmfmac4356-pcie.bin linux-firmware has: >>> version 7.35.180.176 dated 2017-10-23, way before the CVE >>> >>> Where as https://community.cypress.com/docs/DOC-19000 / >>> cypress-fmac-v4.14.77-2020_0115.zip has: >>> version 7.35.180.197 which presumably contains a fix (no changelog) >> >> Ping? >> >> The very old age of the firmware files in linux-firmware is really >> UNACCEPTABLE and very irresponsible from a security POV. Please >> fix this very soon. >> >> If you do not reply to this email I see no choice but to switch >> the firmwares in linux-firmware over to the ones from the SDK which >> you do regularly update, e.g. those from: >> https://community.cypress.com/docs/DOC-19000 >> >> Yes those are under an older, slightly different version of the Cypress >> license, which is less then ideal, but that license is still acceptable >> for linux-firmware (*) and since you are not providing any updates to >> the special builds you have been doing for linux-firmware you are >> really leaving us no option other then switching to the SDK version >> of the firmwares. > > Hans, > > As we discussed previously, those files are not suitable for linux-firmware for the reason of regulatory (blobs are only for Cypress reference boards and could violate regulatory on other boards); But the special builds you are doing for Linux firmware have a clm_blob too, the only difference is that it is embedded. If it is possible to embed a generic version of the clm_blob, then why not provide separate a generic version of the separate clm_blob files, so that those can be used together with build which you release regularly as part of your SDK ? This way you do not need to do special builds for linux-firmware, which seems to be the main bottleneck for having up2date Cypress firmware files inside linux-firmware. > also clm_blob download is not supported in kernels prior to 4.15 so those files won't work with older kernels. That is a valid concern, I'm not sure what the rules for linux-firmware are with regards to this. OTOH those are quite old kernels and if we must choice between having recent firmware for modern kernels or old kernel compatibility I guess the preference would be to have recent firmware. Likely devices using such old kernels are not updating their version of linux-firmware anyways. > Chris owns the Cypress firmware upstream strategy and will explain our going-forward strategy to you. Ok. Regards, Hans