public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: steve@sakoman.com, openembedded-core@lists.openembedded.org
Subject: Re: [OE-core][kirkstone 09/10] qemu: ignore CVE-2023-1386
Date: Thu, 10 Apr 2025 12:32:22 +0100	[thread overview]
Message-ID: <1ac4901e31b26e3b3c0952cb35ed18c298a87a42.camel@linuxfoundation.org> (raw)
In-Reply-To: <b6b026e8e1965f8902780b519aa60bb818f920a5.1744145328.git.steve@sakoman.com>

On Tue, 2025-04-08 at 13:51 -0700, Steve Sakoman via
lists.openembedded.org wrote:
> From: Peter Marko <peter.marko@siemens.com>
> 
> Upstream Repository: https://gitlab.com/qemu-project/qemu.git
> 
> Bug Details:  https://nvd.nist.gov/vuln/detail/CVE-2023-1386
> Type: Security Advisory
> CVE: CVE-2023-1386
> Score: 3.3
> 
> Analysis:
> - According to redhat[1] this CVE has closed as not a bug.
> 
> Reference:
> [1] https://bugzilla.redhat.com/show_bug.cgi?id=2223985
> 
> (From OE-Core rev: 6a5d9e3821246c39ec57fa483802e1bb74fca724)
> 
> Signed-off-by: Madhu Marri <madmarri@cisco.com>
> Signed-off-by: Steve Sakoman <steve@sakoman.com>
> 
> (Converted to old CVE_CHECK_IGNORE syntax)
> 
> Signed-off-by: Peter Marko <peter.marko@siemens.com>
> Signed-off-by: Steve Sakoman <steve@sakoman.com>
> ---
>  meta/recipes-devtools/qemu/qemu.inc | 3 +++
>  1 file changed, 3 insertions(+)
> 
> diff --git a/meta/recipes-devtools/qemu/qemu.inc b/meta/recipes-
> devtools/qemu/qemu.inc
> index bee30cd56f..cae33459e6 100644
> --- a/meta/recipes-devtools/qemu/qemu.inc
> +++ b/meta/recipes-devtools/qemu/qemu.inc
> @@ -161,6 +161,9 @@ CVE_CHECK_IGNORE += "CVE-2023-2680"
>  #       due to the rocker device not falling within the
> virtualization use case.
>  CVE_CHECK_IGNORE += "CVE-2022-36648"
>  
> +# disputed: not an issue as per
> https://bugzilla.redhat.com/show_bug.cgi?id=2223985
> +CVE_CHECK_IGNORE += "CVE-2023-1386"
> +
>  COMPATIBLE_HOST:mipsarchn32 = "null"
>  COMPATIBLE_HOST:mipsarchn64 = "null"
>  COMPATIBLE_HOST:riscv32 = "null"

This merged to master today. It isn't in walnascar though.

Cheers,

Richard


  reply	other threads:[~2025-04-10 11:32 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-08 20:50 [OE-core][kirkstone 00/10] Patch review Steve Sakoman
2025-04-08 20:50 ` [OE-core][kirkstone 01/10] curl: ignore CVE-2025-0725 Steve Sakoman
2025-04-08 20:50 ` [OE-core][kirkstone 02/10] ofono: patch CVE-2024-7537 Steve Sakoman
2025-04-08 20:50 ` [OE-core][kirkstone 03/10] ghostscript: Fix CVE-2025-27830 Steve Sakoman
2025-04-08 20:51 ` [OE-core][kirkstone 04/10] ghostscript: Fix CVE-2025-27831 Steve Sakoman
2025-04-08 20:51 ` [OE-core][kirkstone 05/10] ghostscript: Fix CVE-2025-27832 Steve Sakoman
2025-04-08 20:51 ` [OE-core][kirkstone 06/10] ghostscript: Fix CVE-2025-27834 Steve Sakoman
2025-04-08 20:51 ` [OE-core][kirkstone 07/10] ghostscript: Fix CVE-2025-27835 Steve Sakoman
2025-04-08 20:51 ` [OE-core][kirkstone 08/10] ghostscript: Fix CVE-2025-27836 Steve Sakoman
2025-04-08 20:51 ` [OE-core][kirkstone 09/10] qemu: ignore CVE-2023-1386 Steve Sakoman
2025-04-10 11:32   ` Richard Purdie [this message]
2025-04-08 20:51 ` [OE-core][kirkstone 10/10] glibc: Add single-threaded fast path to rand() Steve Sakoman
2025-04-10 11:33   ` Richard Purdie
2025-04-10 13:49     ` Steve Sakoman
2025-04-10 15:30       ` Randy MacLeod

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=1ac4901e31b26e3b3c0952cb35ed18c298a87a42.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@lists.openembedded.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox