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-18
Date: Thu, 18 Mar 2021 16:47:34 +0800 [thread overview]
Message-ID: <CAGb2v65+YuY7fMz949oJYTBMY8aQ2j841JKHvsutgzOc-n4vOg@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1358 bytes --]
Hi everyone,
Six new issues this week from the Ubuntu tracker:
- CVE-2020-35519 [net/x25: buffer overflow] - fixed
Looks like a few configs still have X.25 enabled:
4.4.y-cip/x86/plathome_obsvx1.config:CONFIG_X25=m
4.19.y-cip-rt/x86/siemens_i386-rt.config:CONFIG_X25=m
5.10.y-cip-rt/x86/siemens_i386-rt_defconfig:CONFIG_X25=m
Maybe they should be revisited? cip-kernel-config also gives warnings
for CONFIG_X25.
- CVE-2021-20219 [improper synchronization in flush_to_ldisc()] -
likely RedHat only
Report mentions incorrect backport in RedHat kernels.
- CVE-2021-20261 [floppy: race condition data corruption] - fixed
No member enables this except:
4.4.y-cip-rt/x86/siemens_i386-rt.config:CONFIG_BLK_DEV_FD=m
which should probably be turned off.
- CVE-2021-28375 [fastrpc: allows sending kernel RPCs] - fixed
No member enables this.
- CVE-2021-28660 [rtl8188eu: array access out-of-bounds] - fixed
No member enables this.
- CVE-2021-3428 [integer overflow in ext4_es_cache_extent] - unclear [1]
Requires a specially-crafted ext4 FS image, so we likely don't care.
Unfortunately Debian's Salsa service, where the Debian kernel security
issue tracker is
hosted, is currently down, so we only have one source of data this week.
Regards
ChenYu
[1] https://lore.kernel.org/stable/20210317151834.GE2541@quack2.suse.cz/
[-- Attachment #2: Type: text/plain, Size: 428 bytes --]
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#6293): https://lists.cip-project.org/g/cip-dev/message/6293
Mute This Topic: https://lists.cip-project.org/mt/81424743/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-18 8:47 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=CAGb2v65+YuY7fMz949oJYTBMY8aQ2j841JKHvsutgzOc-n4vOg@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).