All of lore.kernel.org
 help / color / mirror / Atom feed
From: <nobuhiro1.iwamatsu@toshiba.co.jp>
To: <cip-dev@lists.cip-project.org>
Subject: Re: [cip-dev] New CVE entries in this week
Date: Thu, 25 Nov 2021 08:00:04 +0000	[thread overview]
Message-ID: <TYAPR01MB625214AA3D666DCAF383397892629@TYAPR01MB6252.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <CAODzB9pm61qjStFZ9_GW-w-M2nqiUyrk1aR3-fJhkzfSyNpx-g@mail.gmail.com>

Hi,

> > CVE-2021-4001: bpf: Fix toctou on read-only map''s constant scalar tracking
> >
> > CVSS v3 score is not provided.
> >
> > This bug was introduced in 5.5-rc1 and fixed in 5.16-rc2.  Patch for 5.15 is in stable-rt tree. Patch for 5.4(https://lore.kernel.org/stable/163757721744154@kroah.com/) and 5.10(https://lore.kernel.org/stable/1637577215186161@kroah.com/) are failed to apply. However, this bug was introduced in 5.5-rc1 so 5.4 can be ignored?
> > Fixed status
> >
> > mainline: [353050be4c19e102178ccc05988101887c25ae53]
> >
>
> I attached a patch for 5.10.

Thanks, LGTM.
I think it would be better to add the comment of the conflict fixing.
e.g. https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-5.10.y&id=1ada86999dc84b852fcc32962f4002e939f4beb7

Best regards,
  Nobuhiro

________________________________________
差出人: cip-dev@lists.cip-project.org <cip-dev@lists.cip-project.org> が Masami Ichikawa <masami.ichikawa@miraclelinux.com> の代理で送信
送信日時: 2021年11月25日 14:16
宛先: cip-dev@lists.cip-project.org
件名: Re: [cip-dev] New CVE entries in this week

Hi !

On Thu, Nov 25, 2021 at 11:42 AM Masami Ichikawa via
lists.cip-project.org
<masami.ichikawa=miraclelinux.com@lists.cip-project.org> wrote:
>
> Hi !
>
> It's this week's CVE report.
>
> This week reported two new CVEs.
>
> * New CVEs
>
> CVE-2021-33098: Improper input validation in the Intel(R) Ethernet ixgbe driver for Linux before version 3.17.3 may allow an authenticated user to potentially enable denial of service via local access.
>
> CVSS v3 score is 5.5 MEDIUM.
>
> Intel released fixed version of driver kit. Not sure this CVE affects mainline's source code.
>
> Fixed status
>
> Intel released fixed version of driver kit.
>
> CVE-2021-4001: bpf: Fix toctou on read-only map''s constant scalar tracking
>
> CVSS v3 score is not provided.
>
> This bug was introduced in 5.5-rc1 and fixed in 5.16-rc2.  Patch for 5.15 is in stable-rt tree. Patch for 5.4(https://lore.kernel.org/stable/163757721744154@kroah.com/) and 5.10(https://lore.kernel.org/stable/1637577215186161@kroah.com/) are failed to apply. However, this bug was introduced in 5.5-rc1 so 5.4 can be ignored?
> Fixed status
>
> mainline: [353050be4c19e102178ccc05988101887c25ae53]
>

I attached a patch for 5.10.

> * Updated CVEs
>
> CVE-2021-3640: UAF in sco_send_frame function
>
> 5.10 and 5.15 are fixed this week.
>
> Fixed status
>
> mainline: [99c23da0eed4fd20cae8243f2b51e10e66aa0951]
> stable/5.10: [4dfba42604f08a505f1a1efc69ec5207ea6243de]
> stable/5.14: [2c2b295af72e4e30d17556375e100ae65ac0b896]
> stable/5.15: [b990c219c4c9d4993ef65ea9db73d9497e70f697]
> stable/5.4: [d416020f1a9cc5f903ae66649b2c56d9ad5256ab]
>
> CVE-2021-43975: atlantic: Fix OOB read and write in hw_atl_utils_fw_rpc_wait
>
> The mainline kernel was fixed in 5.16-rc2.
>
> Fixed status
>
> mainline: [b922f622592af76b57cbc566eaeccda0b31a3496]
>
> Currently tracking CVEs
>
> CVE-2021-31615: Unencrypted Bluetooth Low Energy baseband links in
> Bluetooth Core Specifications 4.0 through 5.2
>
> There is no fix information.
>
> CVE-2020-26555: BR/EDR pin code pairing broken
>
> No fix information
>
> CVE-2020-26556: kernel: malleable commitment Bluetooth Mesh Provisioning
>
> No fix information.
>
> CVE-2020-26557: kernel: predictable Authvalue in Bluetooth Mesh
> Provisioning Leads to MITM
>
> No fix information.
>
> CVE-2020-26559: kernel: Authvalue leak in Bluetooth Mesh Provisioning
>
> No fix information.
>
> CVE-2020-26560: kernel: impersonation attack in Bluetooth Mesh Provisioning
>
> No fix information.
>
> Regards,
>
> --
> Masami Ichikawa
> Cybertrust Japan Co., Ltd.
>
> Email :masami.ichikawa@cybertrust.co.jp
>           :masami.ichikawa@miraclelinux.com
>
>
>

Regards,

--
Masami Ichikawa
Cybertrust Japan Co., Ltd.

Email :masami.ichikawa@cybertrust.co.jp
          :masami.ichikawa@miraclelinux.com



  reply	other threads:[~2021-11-25  8:00 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <16BAA9D56D09F20A.23256@lists.cip-project.org>
2021-11-25  5:16 ` [cip-dev] New CVE entries in this week Masami Ichikawa
2021-11-25  8:00   ` nobuhiro1.iwamatsu [this message]
2021-11-25 12:00     ` Masami Ichikawa
2021-11-25  9:09   ` Pavel Machek
2021-11-25 12:01     ` Masami Ichikawa
2022-01-26 23:51 Masami Ichikawa
2022-01-27  8:21 ` [cip-dev] " nobuhiro1.iwamatsu
2022-01-28  6:18   ` Masami Ichikawa
2022-01-29 21:03 ` Pavel Machek
2022-01-31  0:00   ` Masami Ichikawa
  -- strict thread matches above, loose matches on Subject: below --
2022-01-12 23:39 Masami Ichikawa
2022-01-13  8:07 ` [cip-dev] " Pavel Machek
2022-01-13 12:41   ` Masami Ichikawa
2021-12-29 23:29 Masami Ichikawa
2021-12-30 10:20 ` [cip-dev] " Pavel Machek
2021-12-30 23:05   ` Masami Ichikawa
2021-12-23  0:48 Masami Ichikawa
2021-12-23 17:11 ` [cip-dev] " Pavel Machek
2021-12-15 23:49 Masami Ichikawa
2021-12-16  5:26 ` [cip-dev] " nobuhiro1.iwamatsu
2021-12-16  5:58   ` Masami Ichikawa
2021-12-16  8:49 ` Pavel Machek
2021-12-08 23:44 Masami Ichikawa
2021-12-09  9:20 ` [cip-dev] " Pavel Machek
2021-12-09 14:12   ` Masami Ichikawa
2021-11-25  2:41 Masami Ichikawa
2021-11-25  9:14 ` [cip-dev] " Pavel Machek
2021-11-10 23:52 Masami Ichikawa
2021-11-11  9:21 ` [cip-dev] " Pavel Machek
2021-11-11 12:47   ` Masami Ichikawa
2021-11-04  1:11 New CVE Entries " Masami Ichikawa
2021-11-04  9:57 ` [cip-dev] " Pavel Machek
2021-11-04 13:04   ` 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=TYAPR01MB625214AA3D666DCAF383397892629@TYAPR01MB6252.jpnprd01.prod.outlook.com \
    --to=nobuhiro1.iwamatsu@toshiba.co.jp \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.