From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Yegor Yefremov <yegorslists@googlemail.com>
Cc: buildroot@buildroot.org, Bernd Kuhls <bernd@kuhls.net>,
Will Newton <will.newton@gmail.com>
Subject: Re: [Buildroot] [PATCH v2] package/libmicrohttpd: ignore CVE-2025-59777 and CVE-2025-62689
Date: Tue, 13 Oct 2026 16:19:19 +0200 [thread overview]
Message-ID: <as49hKBimzOid79a@windsurf> (raw)
In-Reply-To: <CAGm1_ktftT0eCbujWXYwky+_u18eSbyxDFWoMgrL9r7fw-rKkA@mail.gmail.com>
On Thu, Oct 08, 2026 at 04:01:30PM +0200, Yegor Yefremov wrote:
> > I filed a request a week ago. Till now no answer :-(
>
> I got the answer. Both CVEs are no longer valid for the current
> version. The patch can be dismissed.
Thanks a lot!
In the future: it is fine for me if you send <pkg>_IGNORE_CVES entries
as long as an e-mail to fix the NVD database is also sent. It's a bit
like having the patch locally and upstreaming the fix. Once the fix is
upstreamed (NVD database is fixed), the <pkg>_IGNORE_CVES entry can be
dropped. And if we forget to drop it, the CVE checker tool in
Buildroot is supposed to tell us: "you have a <pkg>_IGNORE_CVES entry
for CVE-YYYY-ABCABC but this CVE isn't affecting the version of the
package in Buildroot", which is a hint that the entry is stale.
Best regards,
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2026-10-13 14:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-01 11:49 [Buildroot] [PATCH v2] package/libmicrohttpd: ignore CVE-2025-59777 and CVE-2025-62689 yegorslists--- via buildroot
2026-09-18 19:50 ` Thomas Petazzoni via buildroot
2026-10-02 13:55 ` Yegor Yefremov via buildroot
2026-10-08 14:01 ` Yegor Yefremov via buildroot
2026-10-13 14:19 ` Thomas Petazzoni via buildroot [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=as49hKBimzOid79a@windsurf \
--to=buildroot@buildroot.org \
--cc=bernd@kuhls.net \
--cc=thomas.petazzoni@bootlin.com \
--cc=will.newton@gmail.com \
--cc=yegorslists@googlemail.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