All of lore.kernel.org
 help / color / mirror / Atom feed
From: Masami Ichikawa <masami256@gmail.com>
To: cip-dev@lists.cip-project.org
Subject: Re: [cip-dev] New CVE entries in this week
Date: Fri, 31 Dec 2021 08:05:04 +0900	[thread overview]
Message-ID: <CACOXgS_1OiUhYqHfCLGPSnmA-8b0Ngp4RvHmPSXwPnrC7cvuLw@mail.gmail.com> (raw)
In-Reply-To: <20211230102038.GA7207@amd>

Hi !

On Thu, Dec 30, 2021 at 7:20 PM Pavel Machek <pavel@denx.de> wrote:
>
> Hi!
>
> > CVE-2021-45469: f2fs: fix to do sanity check on last xattr entry in
> > __f2fs_setxattr()
> >
> > CVSS v3 score is not provided
> >
> > OOB access bug in  __f2fs_setxattr().
> >
> > Although it is fixed in stable trees, the patch isn't merged in the
> > mainline yet at 2021/12/30. The commit 5598b24 ("f2fs: fix to do
> > sanity check on last xattr entry in __f2fs_setxattr()") is in
> > https://git.kernel.org/pub/scm/linux/kernel/git/chao/linux.git/commit/?h=dev&id=5598b24efaf4892741c798b425d543e4bed357a1
> > but not in the mainline.
> >
>
> Interesting. That's wrong and unusual for stable tree.
>
> > CVE-2021-45480: rds: memory leak in __rds_conn_create()
> >
> > CVSS v3 score is not provided
> >
> > This bug was introdued by commit aced3ce57cd3 ("RDS tcp loopback
> > connection can hang") which was merged at 5.13-rc4.
>
> It was also merged in 4.19-stable as 0a3158ac5999fe. That's why we see
> 4.19 tree needing the fix. 4.4 is not affected. Good.
>

Thank you for the information.

> > mainline: [5f9562ebe710c307adc5f666bf1a2162ee7977c0]
> > stable/4.19: [1ed173726c1a0082e9d77c7d5a85411e85bdd983]
>
> 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 (#7310): https://lists.cip-project.org/g/cip-dev/message/7310
> Mute This Topic: https://lists.cip-project.org/mt/88025787/6028936
> Group Owner: cip-dev+owner@lists.cip-project.org
> Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/10394996/6028936/1199334894/xyzzy [masami256@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>

Regards,
-- 
/**
* Masami Ichikawa
* personal: masami256@gmail.com
* fedora project: masami@fedoraproject.org
*/


  reply	other threads:[~2021-12-30 23:05 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-29 23:29 New CVE entries in this week Masami Ichikawa
2021-12-30 10:20 ` [cip-dev] " Pavel Machek
2021-12-30 23:05   ` Masami Ichikawa [this message]
  -- strict thread matches above, loose matches on Subject: below --
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
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-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
     [not found] <16BAA9D56D09F20A.23256@lists.cip-project.org>
2021-11-25  5:16 ` Masami Ichikawa
2021-11-25  8:00   ` nobuhiro1.iwamatsu
2021-11-25 12:00     ` Masami Ichikawa
2021-11-25  9:09   ` Pavel Machek
2021-11-25 12:01     ` 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=CACOXgS_1OiUhYqHfCLGPSnmA-8b0Ngp4RvHmPSXwPnrC7cvuLw@mail.gmail.com \
    --to=masami256@gmail.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 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.