From: Masami Ichikawa <masami.ichikawa@miraclelinux.com>
To: cip-dev <cip-dev@lists.cip-project.org>
Subject: Re: [cip-dev] New CVE entry this week
Date: Thu, 7 Oct 2021 20:38:55 +0900 [thread overview]
Message-ID: <CAODzB9omMdRDC9JxfJie63w0SA5-LKGRaPuNAAe8WbexFMsw7w@mail.gmail.com> (raw)
In-Reply-To: <20211007073054.GA10302@duo.ucw.cz>
Hi !
On Thu, Oct 7, 2021 at 4:31 PM Pavel Machek <pavel@denx.de> wrote:
>
> Hi!
>
> > It's this week's CVE report.
> >
> > This week reported new CVEs.
> >
> > * New CVEs
> >
> > CVE-2021-41864: bpf: Fix integer overflow in prealloc_elems_and_freelist()
> >
> > CVSS v3 score is not provided.
> >
> > Patch 30e29a9a2bc6 (bpf: Fix integer overflow in
> > prealloc_elems_and_freelist()
> ...
> > Fixed status
> >
> > Fix patch has been merged into bpf tree, but not in the mainline yet.
>
> I guess we can wait for this to be merged through normal channels.
>
Yes. I'll track the patch goes into the mainline.
> > * Updated CVEs
> >
> > CVE-2019-19449: mounting a crafted f2fs filesystem image can lead to
> > slab-out-of-bounds read access in f2fs_build_segment_manager in
> > fs/f2fs/segment.c
> >
> > This patch has been merged since 5.10-rc1.
> > For 5.4, patch can be applied via git-am. For 4.4 and 4.19, patch can
> > be applied via git-am with -3 option.
> >
> > Fixed status
> >
> > mainline: [3a22e9ac71585bcb7667e44641f1bbb25295f0ce]
> > stable/5.10: [3a22e9ac71585bcb7667e44641f1bbb25295f0ce]
>
> It may make sense to help with this backport.
>
> > CVE-2021-37159: net: hso: do not call unregister if not registered
> >
> > 4.14, 4.19, and 5.4 have been fixed. 4.4 and 4.9 haven't been fixed
> > yet. However, patch can be applied to 4.4 and 4.9 without any
> > modification. According to cip-kernel-config, no CIP member use HSO
> > module.
>
> Not sure why this has CVE number. We probably need not care.
I agree.
>
> > CVE-2021-38300: bpf, mips: Validate conditional branch offsets
> >
> > This vulnerability is only affected to MIPS architecture. No cip
> > member use MIPS architecture.
> >
> > 5.10 has been fixed. Applying this fix to 4.4, 4.9, 4.19, and 5.4, it
> > needs to modify the patch.
> >
> > Fixed status
> >
> > mainline: [37cb28ec7d3a36a5bace7063a3dba633ab110f8b]
> > stable/5.10: [c61736a994fe68b0e5498e4e84e1c9108dc41075]
>
> I guess we don't care about MIPS.
>
I see. We don't have to track this CVE.
> Best regards,
> Pavel
> --
> DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
> HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#6802): https://lists.cip-project.org/g/cip-dev/message/6802
> Mute This Topic: https://lists.cip-project.org/mt/86134956/4520416
> Group Owner: cip-dev+owner@lists.cip-project.org
> Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129101/4520416/1465703922/xyzzy [masami.ichikawa@miraclelinux.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
Regards,
--
Masami Ichikawa
Cybertrust Japan Co., Ltd.
Email :masami.ichikawa@cybertrust.co.jp
:masami.ichikawa@miraclelinux.com
WARNING: multiple messages have this Message-ID (diff)
From: "Masami Ichikawa" <masami.ichikawa@miraclelinux.com>
To: cip-dev <cip-dev@lists.cip-project.org>
Subject: Re: [cip-dev] New CVE entry this week
Date: Thu, 7 Oct 2021 20:38:55 +0900 [thread overview]
Message-ID: <CAODzB9omMdRDC9JxfJie63w0SA5-LKGRaPuNAAe8WbexFMsw7w@mail.gmail.com> (raw)
Message-ID: <20211007113855.stKNR2PmFLDANn7fx2xRiE156ATXMkAeiskgz44byZ8@z> (raw)
In-Reply-To: <20211007073054.GA10302@duo.ucw.cz>
[-- Attachment #1: Type: text/plain, Size: 2428 bytes --]
Hi !
On Thu, Oct 7, 2021 at 4:31 PM Pavel Machek <pavel@denx.de> wrote:
>
> Hi!
>
> > It's this week's CVE report.
> >
> > This week reported new CVEs.
> >
> > * New CVEs
> >
> > CVE-2021-41864: bpf: Fix integer overflow in prealloc_elems_and_freelist()
> >
> > CVSS v3 score is not provided.
> >
> > Patch 30e29a9a2bc6 (bpf: Fix integer overflow in
> > prealloc_elems_and_freelist()
> ...
> > Fixed status
> >
> > Fix patch has been merged into bpf tree, but not in the mainline yet.
>
> I guess we can wait for this to be merged through normal channels.
>
Yes. I'll track the patch goes into the mainline.
> > * Updated CVEs
> >
> > CVE-2019-19449: mounting a crafted f2fs filesystem image can lead to
> > slab-out-of-bounds read access in f2fs_build_segment_manager in
> > fs/f2fs/segment.c
> >
> > This patch has been merged since 5.10-rc1.
> > For 5.4, patch can be applied via git-am. For 4.4 and 4.19, patch can
> > be applied via git-am with -3 option.
> >
> > Fixed status
> >
> > mainline: [3a22e9ac71585bcb7667e44641f1bbb25295f0ce]
> > stable/5.10: [3a22e9ac71585bcb7667e44641f1bbb25295f0ce]
>
> It may make sense to help with this backport.
>
> > CVE-2021-37159: net: hso: do not call unregister if not registered
> >
> > 4.14, 4.19, and 5.4 have been fixed. 4.4 and 4.9 haven't been fixed
> > yet. However, patch can be applied to 4.4 and 4.9 without any
> > modification. According to cip-kernel-config, no CIP member use HSO
> > module.
>
> Not sure why this has CVE number. We probably need not care.
I agree.
>
> > CVE-2021-38300: bpf, mips: Validate conditional branch offsets
> >
> > This vulnerability is only affected to MIPS architecture. No cip
> > member use MIPS architecture.
> >
> > 5.10 has been fixed. Applying this fix to 4.4, 4.9, 4.19, and 5.4, it
> > needs to modify the patch.
> >
> > Fixed status
> >
> > mainline: [37cb28ec7d3a36a5bace7063a3dba633ab110f8b]
> > stable/5.10: [c61736a994fe68b0e5498e4e84e1c9108dc41075]
>
> I guess we don't care about MIPS.
>
I see. We don't have to track this CVE.
> Best regards,
> Pavel
> --
> DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
> HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
>
>
>
Regards,
--
Masami Ichikawa
Cybertrust Japan Co., Ltd.
Email :masami.ichikawa@cybertrust.co.jp
:masami.ichikawa@miraclelinux.com
[-- Attachment #2: Type: text/plain, Size: 429 bytes --]
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#6804): https://lists.cip-project.org/g/cip-dev/message/6804
Mute This Topic: https://lists.cip-project.org/mt/86134956/4520388
Group Owner: cip-dev+owner@lists.cip-project.org
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/10495289/4520388/727948398/xyzzy [cip-dev@archiver.kernel.org]
-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2021-10-07 11:39 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-07 0:59 New CVE entry this week Masami Ichikawa
2021-10-07 0:59 ` [cip-dev] " Masami Ichikawa
2021-10-07 7:30 ` Pavel Machek
2021-10-07 7:30 ` Pavel Machek
2021-10-07 11:38 ` Masami Ichikawa [this message]
2021-10-07 11:38 ` Masami Ichikawa
-- strict thread matches above, loose matches on Subject: below --
2021-10-21 1:21 Masami Ichikawa
2021-10-21 8:41 ` [cip-dev] " nobuhiro1.iwamatsu
2021-10-21 12:05 ` Masami Ichikawa
2021-10-13 23:54 Masami Ichikawa
2021-10-13 23:54 ` [cip-dev] " Masami Ichikawa
2021-10-14 6:55 ` Pavel Machek
2021-10-14 6:55 ` Pavel Machek
2021-09-30 0:12 Masami Ichikawa
2021-09-30 0:12 ` [cip-dev] " Masami Ichikawa
2021-09-30 6:33 ` nobuhiro1.iwamatsu
2021-09-30 6:33 ` Nobuhiro Iwamatsu
2021-09-30 12:11 ` Masami Ichikawa
2021-09-30 12:11 ` Masami Ichikawa
2021-09-23 1:52 Masami Ichikawa
2021-09-16 0:43 Masami Ichikawa
2021-09-16 4:55 ` Nobuhiro Iwamatsu
2021-09-09 2:39 Masami Ichikawa
2021-09-09 6:41 ` Pavel Machek
2021-09-09 12:23 ` Masami Ichikawa
[not found] ` <CAMLqsBZCbrdOaxhuc81kvZsinS+_bFPp2tpmuVnczC1EXCA3Zg@mail.gmail.com>
2021-09-10 0:40 ` Masami Ichikawa
2021-09-02 1:05 Masami Ichikawa
2021-09-02 6:27 ` Pavel Machek
2021-09-02 7:10 ` Nobuhiro Iwamatsu
2021-09-02 12:17 ` Masami Ichikawa
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=CAODzB9omMdRDC9JxfJie63w0SA5-LKGRaPuNAAe8WbexFMsw7w@mail.gmail.com \
--to=masami.ichikawa@miraclelinux.com \
--cc=cip-dev@lists.cip-project.org \
/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).