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>
Subject: [cip-dev] Cip-kernel-sec Updates for Week of 2020-12-03
Date: Thu, 3 Dec 2020 17:26:33 +0800 [thread overview]
Message-ID: <CAGb2v65t+cryAJ+POQX74MH4st7pcf3X_WQohEWJ6j7bMVRQqg@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 874 bytes --]
New issues:
- CVE-2019-20934 [fair scheduler UAF in NUMA code]
- CVE-2020-27815 [fs/jfs: array index out-of-bounds]
- CVE-2020-29368 [mm/THP: COW race condition]
- CVE-2020-29369 [mm/mmap: race condition between expand functions and munmap]
- CVE-2020-29370 [mm/slub: missing TID increment]
- CVE-2020-29371 [fs/romfs: uninitialized memory leaked to userspace]
- CVE-2020-29372 [fs/io_uring: IORING_OP_MADVISE race condition]
- CVE-2020-29373 [fs/io_uring: mount namespace escape]
- CVE-2020-29374 [mm/gup: get_user_pages() and COW ambiguity]
All are fixed in all relevant stable kernels or (CVE-2020-27815) have
fixes queued up for mainline.
Old issues now marked as fixed:
- CVE-2020-10135 [bluetooth: BR/EDR Bluetooth Impersonation Attacks (BIAS)]
Fixes found from backport request.
All in all no action is required for CIP kernels this week.
Regards
ChenYu
Moxa
[-- Attachment #2: Type: text/plain, Size: 420 bytes --]
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#5936): https://lists.cip-project.org/g/cip-dev/message/5936
Mute This Topic: https://lists.cip-project.org/mt/78681021/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]
-=-=-=-=-=-=-=-=-=-=-=-
reply other threads:[~2020-12-03 9:26 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=CAGb2v65t+cryAJ+POQX74MH4st7pcf3X_WQohEWJ6j7bMVRQqg@mail.gmail.com \
--to=wens@csie.org \
--cc=cip-dev@lists.cip-project.org \
--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).