All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Pavel Machek" <pavel@denx.de>
To: cip-dev@lists.cip-project.org
Subject: Re: [cip-dev] New CVE entry this week
Date: Thu, 9 Sep 2021 08:41:49 +0200	[thread overview]
Message-ID: <20210909064148.GA5892@amd> (raw)
In-Reply-To: <CAODzB9oqUztiFZjcd0=dSBJ-bDjfdZ4eW8R69=m0fuZmKOb0qg@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1100 bytes --]

Hi!

> CVE-2021-3759: memcg: charge semaphores and sem_undo objects
> 
> This causes DoS attack. Patch was merged into mainline this week.
> 
> for 4.19, it needs modify or apply following patches to apply commit
> 18319498fdd4.

I don't think we need to care about this one. Embedded systems don't
usually run untrusted code...

> CVE-2021-40490: A race condition was discovered in
> ext4_write_inline_data_end in fs/ext4/inline.c in the ext4 subsystem
> in the Linux kernel through 5.13.13.

This is already queued to 4.4 and 4.19; we can simply wait.

> CVE-2021-38198: KVM: X86: MMU: Use the correct inherited permissions
> to get shadow page
> 
> 4.14 has been fixed this week.
> 
> mainline: [b1bd5cba3306691c771d558e94baa73e8b0b96b7]
> stable/4.14: [cea9e8ee3b8059bd2b36d68f1f428d165e5d13ce]

KVM. Tricky code and not exactly focus on CIP code. But perhaps
someone fixes it for us :-).

Best regards,
								Pavel
-- 
DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany

[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

[-- Attachment #2: Type: text/plain, Size: 429 bytes --]


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#6720): https://lists.cip-project.org/g/cip-dev/message/6720
Mute This Topic: https://lists.cip-project.org/mt/85476557/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]
-=-=-=-=-=-=-=-=-=-=-=-


  reply	other threads:[~2021-09-09  7:08 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-09  2:39 [cip-dev] New CVE entry this week Masami Ichikawa
2021-09-09  6:41 ` Pavel Machek [this message]
2021-09-09 12:23   ` Masami Ichikawa
     [not found] ` <CAMLqsBZCbrdOaxhuc81kvZsinS+_bFPp2tpmuVnczC1EXCA3Zg@mail.gmail.com>
2021-09-10  0:40   ` 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 ` Masami Ichikawa
2021-10-14  6:55   ` Pavel Machek
2021-10-14  6:55     ` Pavel Machek
2021-10-07  0:59 Masami Ichikawa
2021-10-07  0:59 ` Masami Ichikawa
2021-10-07  7:30   ` Pavel Machek
2021-10-07  7:30     ` Pavel Machek
2021-10-07 11:38     ` Masami Ichikawa
2021-10-07 11:38       ` Masami Ichikawa
2021-09-30  0:12 Masami Ichikawa
2021-09-30  0:12 ` 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-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=20210909064148.GA5892@amd \
    --to=pavel@denx.de \
    --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.