cip-dev.lists.cip-project.org archive mirror
 help / color / mirror / Atom feed
From: "Chen-Yu Tsai (Moxa)" <wens@csie.org>
To: cip-dev@lists.cip-project.org
Cc: Pavel Machek <pavel@denx.de>,
	Nobuhiro Iwamatsu <nobuhiro1.iwamatsu@toshiba.co.jp>,
	 masashi.kudo@cybertrust.co.jp
Subject: [cip-dev] Cip-kernel-sec Updates for Week of 2021-04-08
Date: Thu, 8 Apr 2021 15:23:49 +0800	[thread overview]
Message-ID: <CAGb2v66M1mjZjBfHAwv1yECqCDHALzk4_fVD-bdB0V-4R=DPLg@mail.gmail.com> (raw)

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

Hi everyone,

Eight new issues this week:

- CVE-2020-36310 [x86/kvm: svm: infinite loop] - fixed
  auto-backport failed.
- CVE-2020-36311 [x86/kvm: svm: sev: softhang] - fixed (ignore for CIP)
- CVE-2020-36312 [kvm: mem leak] - fixed
- CVE-2020-36313 [kvm: out-of-bounds access] - fixed
- CVE-2021-29657 [x86/kvm: svm: data race] - fixed
- CVE-2021-30002 [media/v4l2: ioctl mem leak] - fixed
- CVE-2021-30178 [x86/kvm: hyperv: NULL ptr deref] - fixed
- CVE-2021-3483 [firewire: nosy: UAF] - fixed (ignore for CIP) - fixed

No updates on CVE-2021-3444, CVE-2021-20292 or CVE-2021-29650 from
previous weeks.


Regards
ChenYu

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


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#6354): https://lists.cip-project.org/g/cip-dev/message/6354
Mute This Topic: https://lists.cip-project.org/mt/81936606/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-04-08  7:24 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='CAGb2v66M1mjZjBfHAwv1yECqCDHALzk4_fVD-bdB0V-4R=DPLg@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 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).