public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: "Yoann Congal" <yoann.congal@smile.fr>
To: <adarsh.jagadish.kamini@est.tech>,
	<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core][whinlatter][PATCH] expat: mark CVE-2025-66382 as vulnerable-investigating
Date: Wed, 22 Apr 2026 11:11:54 +0200	[thread overview]
Message-ID: <DHZKFY8ILV2M.QM2AAGL87S7U@smile.fr> (raw)
In-Reply-To: <20260422085436.320259-1-adarsh.jagadish.kamini@est.tech>

On Wed Apr 22, 2026 at 10:54 AM CEST, Adarsh Jagadish Kamini via lists.openembedded.org wrote:
> From: Adarsh Jagadish Kamini <adarsh.jagadish.kamini@est.tech>
>
> No fix is available yet for CVE-2025-66382 [1].
>
> CVE_STATUS[CVE-2025-66382] = "vulnerable-investigating: no fix available yet"
>
> [1] https://www.cve.org/CVERecord?id=CVE-2025-66382
>
> Signed-off-by: Adarsh Jagadish Kamini <adarsh.jagadish.kamini@est.tech>
> ---

Sorry, but that will be too late for whinlatter. I finished reviewing
the branch and will start the release build soon.

Regards,

>  meta/recipes-core/expat/expat_2.7.4.bb | 1 +
>  1 file changed, 1 insertion(+)
>
> diff --git a/meta/recipes-core/expat/expat_2.7.4.bb b/meta/recipes-core/expat/expat_2.7.4.bb
> index f1eff49688..65aee9d17f 100644
> --- a/meta/recipes-core/expat/expat_2.7.4.bb
> +++ b/meta/recipes-core/expat/expat_2.7.4.bb
> @@ -36,3 +36,4 @@ do_install_ptest:class-target() {
>  BBCLASSEXTEND += "native nativesdk"
>  
>  CVE_PRODUCT = "expat libexpat"
> +CVE_STATUS[CVE-2025-66382] = "vulnerable-investigating: no fix available yet"


-- 
Yoann Congal
Smile ECS



  reply	other threads:[~2026-04-22  9:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-22  8:54 [OE-core][whinlatter][PATCH] expat: mark CVE-2025-66382 as vulnerable-investigating Adarsh Jagadish Kamini
2026-04-22  9:11 ` Yoann Congal [this message]
2026-04-23 12:12   ` Adarsh Jagadish Kamini

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=DHZKFY8ILV2M.QM2AAGL87S7U@smile.fr \
    --to=yoann.congal@smile.fr \
    --cc=adarsh.jagadish.kamini@est.tech \
    --cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox