All of lore.kernel.org
 help / color / mirror / Atom feed
From: richard.purdie@linuxfoundation.org
To: Marta Rybczynska <rybczynska@gmail.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>,
	Ross Burton <ross.burton@arm.com>,
	Steve Sakoman <steve@sakoman.com>
Subject: Re: [OE-core] [PATCH 2/2] freetype: Upgrade 2.12.0 -> 2.12.1
Date: Tue, 10 May 2022 16:42:02 +0100	[thread overview]
Message-ID: <a2de54fa833b5dc25a3a75695632877057a90167.camel@linuxfoundation.org> (raw)
In-Reply-To: <CAApg2=Tx+WXk4U16j61GHLb6KFwfOdXxyrsXLVUQAwN2nePOxA@mail.gmail.com>

On Tue, 2022-05-10 at 17:02 +0200, Marta Rybczynska wrote:
> On Mon, May 9, 2022 at 4:42 PM Marta Rybczynska via
> lists.openembedded.org <rybczynska=gmail.com@lists.openembedded.org>
> wrote:
> > On Mon, May 9, 2022 at 12:40 PM Marta Rybczynska
> > <rybczynska@gmail.com> wrote:
> > > On Sun, May 8, 2022 at 6:45 PM Richard Purdie
> > > <richard.purdie@linuxfoundation.org> wrote:
> > > > On Sun, 2022-05-08 at 13:34 +0100, Richard Purdie via
> > > > lists.openembedded.org wrote:
> > > > > Includes fixes for CVE-2022-27404, CVE-2022-27405, CVE-2022-
> > > > > 27406.
> > > > > 
> > > > > 
> > > > 
> > > > I'm amending this to "Include fix for CVE-2022-27404" since
> > > > CVE-2022-
> > > > 27405 and CVE-2022-27406 were already in 2.12.0.
> > > > 
> > > > I don't think the CVE checker is going to like these as they're
> > > > using
> > > > dates for these for reasons I don't understand.
> > > > 
> > > > 
> > > 
> > > 
> > > They also include versions in the NVD, but there is no version
> > > "non-afected"
> > > as of today for CVE-2022-27404. I'll figure out the exact
> > > versions for those
> > > CVEs and update the NVD in the next hours.
> > > 
> > > Kind regards,
> > > Marta
> > > 
> > 
> > 
> > Update: the message to NVD has been sent. According to my analysis
> > all three
> > CVEs have been fixed in 2.12.0.
> > 
> 
> 
> The change is up in NVD. The next run of the cve-check should see it.

Great, thanks for sorting that one out, the reports will be much better
for it!

Cheers,

Richard



      reply	other threads:[~2022-05-10 15:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-08 12:34 [PATCH 1/2] vim: Upgrade 8.2.4681 -> 8.2.4912 Richard Purdie
2022-05-08 12:34 ` [PATCH 2/2] freetype: Upgrade 2.12.0 -> 2.12.1 Richard Purdie
     [not found] ` <16ED214F51D113CA.5869@lists.openembedded.org>
2022-05-08 16:45   ` [OE-core] " richard.purdie
2022-05-09 10:40     ` Marta Rybczynska
2022-05-09 14:41       ` Marta Rybczynska
     [not found]       ` <16ED76DCD3B51CA1.18911@lists.openembedded.org>
2022-05-10 15:02         ` Marta Rybczynska
2022-05-10 15:42           ` richard.purdie [this message]

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=a2de54fa833b5dc25a3a75695632877057a90167.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=ross.burton@arm.com \
    --cc=rybczynska@gmail.com \
    --cc=steve@sakoman.com \
    /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.