openembedded-core.lists.openembedded.org archive mirror
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Geoffrey GIRY <geoffrey.giry@smile.fr>,
	 openembedded-core@lists.openembedded.org,
	Bruce Ashfield <bruce.ashfield@gmail.com>
Cc: Yoann Congal <yoann.congal@smile.fr>
Subject: Re: [OE-core] [PATCH] cve-extra-exclusions: ignore inapplicable linux-yocto CVEs
Date: Wed, 01 Mar 2023 14:11:19 +0000	[thread overview]
Message-ID: <4b3623567692b08b281fc2157701dfae310c3229.camel@linuxfoundation.org> (raw)
In-Reply-To: <20230227110027.804671-1-geoffrey.giry@smile.fr>

On Mon, 2023-02-27 at 12:00 +0100, Geoffrey GIRY wrote:
> Multiple CVE are patched in kernel but appears as active because the NVD
> database is not up to date.
> 
> CVE are ignored if and only if all versions of kernel used by master are patched.
> 
> Also ignore CVEs with wrong CPE (applied to kernel but actually are for
>  another package)
> 
> Signed-off-by: Geoffrey GIRY <geoffrey.giry@smile.fr>
> Reviewed-by: Yoann Congal <yoann.congal@smile.fr>
> ---
>  .../distro/include/cve-extra-exclusions.inc   | 296 ++++++++++++++++++
>  1 file changed, 296 insertions(+)

FWIW, with this applied, the list reported by our tooling was reduced
to:

https://autobuilder.yocto.io/pub/non-release/patchmetrics/cve-status-master.txt

Cheers,

Richard


  parent reply	other threads:[~2023-03-01 14:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-27 11:00 [PATCH] cve-extra-exclusions: ignore inapplicable linux-yocto CVEs Geoffrey GIRY
2023-02-27 17:49 ` [OE-core] " Marta Rybczynska
2023-02-27 22:02   ` Richard Purdie
2023-02-28  9:05     ` Geoffrey GIRY
2023-02-28 20:41       ` Marta Rybczynska
2023-03-01 10:43       ` Richard Purdie
2023-03-01 14:11 ` Richard Purdie [this message]
2023-03-01 14:37   ` Mikko Rapeli
2023-03-02 15:46     ` Geoffrey GIRY
2023-06-06  5:33 ` Clarifying CVEs for NVD (Was: Re: [OE-core] [PATCH] cve-extra-exclusions: ignore inapplicable linux-yocto CVEs) Marta Rybczynska
2023-06-06 12:35   ` Marko, Peter

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=4b3623567692b08b281fc2157701dfae310c3229.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=bruce.ashfield@gmail.com \
    --cc=geoffrey.giry@smile.fr \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=yoann.congal@smile.fr \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).