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-03-04
Date: Thu, 4 Mar 2021 12:38:21 +0800 [thread overview]
Message-ID: <CAGb2v66D2t0asUDNafOi+fLwAyt0sLqZ2TMjEuz=JtTaPA6GLw@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 844 bytes --]
Hi,
This week there are three new issues:
- CVE-2021-0399 [net/xt_qtaguid] - Android kernel only
- CVE-2021-0447 [l2tp] - Fixed in all kernels
- CVE-2021-0448 [netfilter/ctnetlink] - Duplicate of CVE-2020-25211.
Fixed in all kernels.
In addition, CVE-2020-25639 (nVidia / nouveau) is now fixed.
CVE-2020-29368 requires another patch for 4.9, which is queued up for
4.9.259.
I also added CVE-2020-27067, which was missing from our archive.
This is a superset of CVE-2021-0447, and is already fixed.
Last, I fixed a bug in the Debian import script that I introduced
last week. Fixes spanning multiple releases should now be parsed
correctly. The Ubuntu import script was fixed to correctly parse
alternative comment styles. Comments from Ubuntu maintainers are
now correctly grouped.
Regards
ChenYu
[-- Attachment #2: Type: text/plain, Size: 428 bytes --]
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#6207): https://lists.cip-project.org/g/cip-dev/message/6207
Mute This Topic: https://lists.cip-project.org/mt/81070928/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-03-04 4:38 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='CAGb2v66D2t0asUDNafOi+fLwAyt0sLqZ2TMjEuz=JtTaPA6GLw@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).