From: "Ben Hutchings" <ben.hutchings@codethink.co.uk>
To: cip-dev@lists.cip-project.org, nobuhiro1.iwamatsu@toshiba.co.jp,
jan.kiszka@siemens.com
Subject: Re: [cip-dev] Backporting of security patches for Intel i40e drivers required?
Date: Wed, 11 Nov 2020 20:50:02 +0000 [thread overview]
Message-ID: <9c52fda6f710d3aad6fd9f781b33c4034dee4d10.camel@codethink.co.uk> (raw)
In-Reply-To: <TY2PR01MB4972EDB29B2AB0B3AE5E363DA0E80@TY2PR01MB4972.jpnprd01.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 1386 bytes --]
On Wed, 2020-11-11 at 13:18 +0000, masashi.kudo@cybertrust.co.jp wrote:
> Hi,
>
> The other day, I inquired about CVE-2019-0145, CVE-2019-0147, and CVE-2019-0148 in the following email.
>
> The kernel team discussed for weeks how to deal with them.
> As a result of these discussions, we concluded to ignore them until Intel fixes issues, because:
> - The descriptions of patches are not clear, and we cannot figure out what is right
> - The patches we identified do not really look like fixing too serious stuff.
They all seemed to involve communication with the owner of a PCIe
Virtual Function (VF). A VF might be assigned to a VM or privileged
process. In Civil Infrastructure systems those should already be
trusted and so the issues don't matter that much.
> So far, we had the following AI, but we close this based on the above situation.
>
> 2. Check whether CVE-2019-0145, CVE-2019-0147, CVE-2019-0148 needs to be backported to 4.4 - Kernel Team
[...]
Well, I found it quite easy to backport the applicable parts of the
fixes. I already sent them along with some other fixes for the 4.14
and 4.9 branches, and could still do so for 4.4.
Ben.
--
Ben Hutchings, Software Developer Codethink Ltd
https://www.codethink.co.uk/ Dale House, 35 Dale Street
Manchester, M1 2HF, United Kingdom
[-- Attachment #2: Type: text/plain, Size: 420 bytes --]
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#5791): https://lists.cip-project.org/g/cip-dev/message/5791
Mute This Topic: https://lists.cip-project.org/mt/77380165/4520388
Group Owner: cip-dev+owner@lists.cip-project.org
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/727948398/xyzzy [cip-dev@archiver.kernel.org]
-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2020-11-11 20:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-08 9:42 [cip-dev] Backporting of security patches for Intel i40e drivers required? masashi.kudo
2020-10-09 0:23 ` Nobuhiro Iwamatsu
2020-10-09 7:24 ` Jan Kiszka
2020-10-12 9:27 ` masashi.kudo
2020-10-14 14:13 ` Pavel Machek
2020-10-14 14:55 ` Chen-Yu Tsai (Moxa)
2020-11-11 13:18 ` masashi.kudo
2020-11-11 20:50 ` Ben Hutchings [this message]
2020-11-13 0:49 ` masashi.kudo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9c52fda6f710d3aad6fd9f781b33c4034dee4d10.camel@codethink.co.uk \
--to=ben.hutchings@codethink.co.uk \
--cc=cip-dev@lists.cip-project.org \
--cc=jan.kiszka@siemens.com \
--cc=nobuhiro1.iwamatsu@toshiba.co.jp \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).