All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Chen-Yu Tsai (Moxa)" <wens@csie.org>
To: Pavel Machek <pavel@denx.de>,
	Nobuhiro Iwamatsu <nobuhiro1.iwamatsu@toshiba.co.jp>,
	 masashi.kudo@cybertrust.co.jp
Cc: cip-dev@lists.cip-project.org
Subject: [cip-dev] Cip-kernel-sec Updates for Week of 2021-02-25
Date: Thu, 25 Feb 2021 00:54:52 +0800	[thread overview]
Message-ID: <CAGb2v65e+un0E5SwvhNShDz2MObJFZU7DsMvFXN077dSRQdEMQ@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1093 bytes --]

Hi everyone,

Five new issues this week:
- CVE-2020-24502 [e810: local DoS] - out-of-tree?
- CVE-2020-24503 [e810: local information leak] - out-of-tree?
- CVE-2020-24504 [e810: local DoS] - out-of-tree?
- CVE-2020-35501 [auditd: open_by_handle_at not covered by file watch] - no fix
- CVE-2021-3411 [broken KRETPROBES on x86] - fixed

Regarding e810, the Intel advisory [1] seems to be referring to the
out-of-tree driver, of which version 1.0.4 was released on 7/14/2020.

Also, a bug was found in the Debian import script. The script was not
picking up fixes which spanned multiple stable kernel releases. This
has now been fixed and a re-import was attempted, though it may be
insufficient to fix all the data already in the repository.

Last, CVE-2020-12362, CVE-2020-12363, and CVE-2020-12364 are now known
to be fixed by a firmware update. However to use the new firmware, a
kernel patch [2] is required.


Regards
ChenYu

[1] https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-00462.html
[2] https://git.kernel.org/linus/c784e5249e773689e38d2bc1749f08b986621a26

[-- Attachment #2: Type: text/plain, Size: 428 bytes --]


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#6194): https://lists.cip-project.org/g/cip-dev/message/6194
Mute This Topic: https://lists.cip-project.org/mt/80881316/4520388
Group Owner: cip-dev+owner@lists.cip-project.org
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/4520388/727948398/xyzzy [cip-dev@archiver.kernel.org]
-=-=-=-=-=-=-=-=-=-=-=-


                 reply	other threads:[~2021-02-24 16:55 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=CAGb2v65e+un0E5SwvhNShDz2MObJFZU7DsMvFXN077dSRQdEMQ@mail.gmail.com \
    --to=wens@csie.org \
    --cc=cip-dev@lists.cip-project.org \
    --cc=masashi.kudo@cybertrust.co.jp \
    --cc=nobuhiro1.iwamatsu@toshiba.co.jp \
    --cc=pavel@denx.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.