From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Julien Olivain <ju.o@free.fr>
Cc: buildroot@buildroot.org, Romain Naour <romain.naour@gmail.com>,
Thomas Perale <thomas.perale@mind.be>
Subject: Re: [Buildroot] [PATCH 1/1] package/glibc: add CVE-2025-15281 CVE-2026-0861 CVE-2026-0915 to _IGNORE_CVES
Date: Wed, 4 Feb 2026 09:56:53 +0100 [thread overview]
Message-ID: <aYMJx0dgzwrcP_9O@windsurf> (raw)
In-Reply-To: <20260125114310.246433-1-ju.o@free.fr>
On Sun, Jan 25, 2026 at 12:43:10PM +0100, Julien Olivain via buildroot wrote:
> Commit [1] bumped glibc from 2.42-3-gbc13db739 to 2.42-51-gcbf39c26b
> to fix some CVEs, but forgot to add those CVEs to GLIBC_IGNORE_CVES.
> This was needed because the GLIBC_CPE_ID_VERSION used for CVE checks
> remains to the same value "2.42" which is marked as vulnerable to
> those CVEs.
>
> This commit adds those _IGNORE_CVES with the corresponding upstream
> commit references, to make sure they will not be reported by the
> "make pkg-stats" command.
>
> Fixes:
> - [1]
>
> [1] https://gitlab.com/buildroot.org/buildroot/-/commit/18de297a5ad3d1fc1b44f54ae69289ca10200ad5
>
> Cc: Waldemar Brodkorb <wbx@openadk.org>
> Cc: Thomas Perale <thomas.perale@mind.be>
> Signed-off-by: Julien Olivain <ju.o@free.fr>
Applied, thanks!
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
next prev parent reply other threads:[~2026-02-04 8:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-25 11:43 [Buildroot] [PATCH 1/1] package/glibc: add CVE-2025-15281 CVE-2026-0861 CVE-2026-0915 to _IGNORE_CVES Julien Olivain via buildroot
2026-02-04 8:56 ` Thomas Petazzoni via buildroot [this message]
2026-02-13 19:37 ` Thomas Perale via buildroot
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=aYMJx0dgzwrcP_9O@windsurf \
--to=buildroot@buildroot.org \
--cc=ju.o@free.fr \
--cc=romain.naour@gmail.com \
--cc=thomas.perale@mind.be \
--cc=thomas.petazzoni@bootlin.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