From: "Roland Kovács" <roland.kovacs@est.tech>
To: "openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>,
"yoann.congal@smile.fr" <yoann.congal@smile.fr>
Subject: Re: [OE-core] [scarthgap][PATCH v2] gnupg: Mark CVE-2025-68972 as upstream-wontfix
Date: Mon, 31 Aug 2026 16:00:52 +0000 [thread overview]
Message-ID: <0e1dee06745f0473fdd9fa2ee444332c2cd97ea0.camel@est.tech> (raw)
In-Reply-To: <DL371ZPMRYMX.3Q2T6B000L34F@smile.fr>
On Mon, 2026-08-31 at 16:21 +0200, Yoann Congal wrote:
> On Fri Aug 21, 2026 at 11:30 AM CEST, Roland Kovács via lists.openembedded.org wrote:
> > Mark CVE-2025-68972 as upstream-wontfix based on mailing list discussion,
> > where the maintainer states that "[...] this is wrong usage of a tool or social
> > engineering".
> >
> > Link: https://lists.gnupg.org/pipermail/gnupg-devel/2026-January/036154.html
> >
> > Signed-off-by: Roland Kovacs <roland.kovacs@est.tech>
> > ---
> > v1: https://lists.openembedded.org/g/openembedded-core/message/243897
> > v1 -> v2:
> > - Fix patchtest complaint about empty commit message.
> > meta/recipes-support/gnupg/gnupg_2.4.9.bb | 1 +
> > 1 file changed, 1 insertion(+)
> >
> > diff --git a/meta/recipes-support/gnupg/gnupg_2.4.9.bb b/meta/recipes-
> > support/gnupg/gnupg_2.4.9.bb
> > index c85de6047f..3ebea399d7 100644
> > --- a/meta/recipes-support/gnupg/gnupg_2.4.9.bb
> > +++ b/meta/recipes-support/gnupg/gnupg_2.4.9.bb
> > @@ -85,3 +85,4 @@ lcl_maybe_fortify:mipsarch = ""
> >
> > CVE_STATUS[CVE-2022-3219] = "upstream-wontfix: Upstream doesn't seem to be keen on merging the
> > proposed commit - https://dev.gnupg.org/T5993"
> > CVE_STATUS[CVE-2025-30258] = "cpe-stable-backport: fir for this CVE was backported to version
> > 2.4.8"
> > +CVE_STATUS[CVE-2025-68972] = "upstream-wontfix: Upstream considers this CVE invalid -
> > https://lists.gnupg.org/pipermail/gnupg-devel/2026-January/036154.html"
>
> Hello,
>
> I don't think we need this fix since MITRE data shows CVE-2025-68972 only
> affect <= 2.4.8 and we are at 2.4.9.
>
> Regards,
Hi Yoann,
Sorry about it, feel free to drop!
It probably got in my queue before the recipe update, and I was just slow to react. :)
It's also possible that it is showing up on my side because debian tracker still marks this version
vulnerable (and we aggregate the sources).
https://security-tracker.debian.org/tracker/CVE-2025-68972
Cheers,
Roland
prev parent reply other threads:[~2026-08-31 16:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-21 9:30 [scarthgap][PATCH v2] gnupg: Mark CVE-2025-68972 as upstream-wontfix Roland Kovacs
2026-08-31 14:21 ` [OE-core] " Yoann Congal
2026-08-31 16:00 ` Roland Kovács [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=0e1dee06745f0473fdd9fa2ee444332c2cd97ea0.camel@est.tech \
--to=roland.kovacs@est.tech \
--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 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.