All of lore.kernel.org
 help / color / mirror / Atom feed
From: Masami Ichikawa <masami.ichikawa@miraclelinux.com>
To: cip-dev@lists.cip-project.org
Subject: Re: [cip-dev] New CVE entries in this week
Date: Mon, 31 Jan 2022 09:00:54 +0900	[thread overview]
Message-ID: <CAODzB9rTUkKmDsLszDvci47oW5Ua7Oc-S01-w5_BYXk9ukUaSQ@mail.gmail.com> (raw)
In-Reply-To: <20220129210347.GA27693@duo.ucw.cz>

Hi !

On Sun, Jan 30, 2022 at 6:03 AM Pavel Machek <pavel@denx.de> wrote:
>
> Hi!
> >
>
> > CVE-2022-0330: drm/i915: Flush TLBs before releasing backing store
> >
> > CVSS v3 score is not provided
> >
> > Vulnerability in the i915 driver. Without an active IOMMU malicious
> > userspace can gain access (from the
> > code executing on the GPU) to random memory pages.
> >
> > Fixed status
> >
> > mainline: [7938d61591d33394a21bdd7797a245b65428f44c]
>
> Wow. This must have been important. It looks like 5.10.95 (+4.4 and
> 4.19) was released just to get this fixed. Fix is "interesting" but...
> it should be fixed.
>

Yes. Stable kernels were fixed :)

stable/4.14: [eed39c1918f1803948d736c444bfacba2a482ad0]
stable/4.19: [b188780649081782e341e52223db47c49f172712]
stable/4.4: [db6a2082d5a2ebc5ffa41f7213a544d55f73793a]
stable/4.9: [84f4ab5b47d955ad2bb30115d7841d3e8f0994f4]
stable/5.10: [6a6acf927895c38bdd9f3cd76b8dbfc25ac03e88]
stable/5.15: [8a17a077e7e9ecce25c95dbdb27843d2d6c2f0f7]
stable/5.16: [ec1b6497a2bc0293c064337e981ea1f6cbe57930]
stable/5.4: [1b5553c79d52f17e735cd924ff2178a2409e6d0b]


> 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 (#7517): https://lists.cip-project.org/g/cip-dev/message/7517
> Mute This Topic: https://lists.cip-project.org/mt/88710351/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


  reply	other threads:[~2022-01-31  0:01 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-26 23:51 New CVE entries in this week 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 [this message]
  -- 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
     [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=CAODzB9rTUkKmDsLszDvci47oW5Ua7Oc-S01-w5_BYXk9ukUaSQ@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 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.