From: Julien Olivain via buildroot <buildroot@buildroot.org>
To: Francois Perrad <francois.perrad@gadz.org>
Cc: buildroot@busybox.net
Subject: Re: [Buildroot] [PATCH] package/perl: bump to version 5.42.0
Date: Sat, 13 Dec 2025 16:58:09 +0100 [thread overview]
Message-ID: <bf8d7a90ae96e613006d805d2ff603ff@free.fr> (raw)
In-Reply-To: <20251212085421.76507-1-francois.perrad@gadz.org>
Hi Francois,
Thanks for the patch.
On 12/12/2025 09:54, Francois Perrad via buildroot wrote:
> Signed-off-by: Francois Perrad <francois.perrad@gadz.org>
Looking at the release notes of this version at:
https://perldoc.perl.org/5.42.0/perldelta
I see that this new version fixes:
https://www.cve.org/CVERecord?id=CVE-2025-40909
The other CVE-2024-56406 mentioned was fixed in:
https://gitlab.com/buildroot.org/buildroot/-/commit/164c84ee9b820f5b21e79b4d52c07a613925d3f2
Could you confirm that CVE-2025-40909 applies to Buildroot?
If it does apply, could you send an updated patch marked as
"security bump", including the links release notes and CVE,
please?
Best regards,
Julien.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2025-12-13 15:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-12 8:54 [Buildroot] [PATCH] package/perl: bump to version 5.42.0 Francois Perrad via buildroot
2025-12-13 15:58 ` Julien Olivain via buildroot [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-12-19 6:45 Francois Perrad via buildroot
2025-12-19 18:02 ` Julien Olivain 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=bf8d7a90ae96e613006d805d2ff603ff@free.fr \
--to=buildroot@buildroot.org \
--cc=buildroot@busybox.net \
--cc=francois.perrad@gadz.org \
--cc=ju.o@free.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.