From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: <yoann.congal@smile.fr>, <openembedded-core@lists.openembedded.org>
Cc: "Thomas Petazzoni" <thomas.petazzoni@bootlin.com>
Subject: Re: [OE-core] [PATCH 22/24] libpcre2: upgrade 10.48 -> 10.49
Date: Mon, 05 Oct 2026 17:34:03 +0200 [thread overview]
Message-ID: <DLX0IZJ8VAS9.334U1B5L5ZG53@bootlin.com> (raw)
In-Reply-To: <DLWSAC7YXK30.1G1YB5HCJTRHP@smile.fr>
On Mon Oct 5, 2026 at 11:06 AM CEST, Yoann Congal via lists.openembedded.org wrote:
> On Wed Sep 30, 2026 at 10:16 AM CEST, Mathieu Dubois-Briand via lists.openembedded.org wrote:
>> Version 10.49 28-September-2026
>> -------------------------------
>>
>> This is a security-only release, to address GHSA-r9hj-j2rw-4q3m.
>>
>> Compared to 10.48, this release has only a minimal code change to prevent an
>> out-of-bounds write with arbitrary data. An attacker-controlled regex pattern
>> is required, and applications are only affected if using the
>> pcre2_jit_stack_create() and pcre2_jit_stack_assign() APIs to provide a growable
>> JIT stack, and then matching against a pattern with unusually high JIT stack
>> usage, such as a large number of capturing groups.
>>
>> The implications of an out-of-bounds write could include arbitrary code
>> execution.
>>
>> The issue is not a regression and affects releases 10.48 and earlier.
>>
>> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
>> ---
>> meta/recipes-support/libpcre/{libpcre2_10.48.bb => libpcre2_10.49.bb} | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/meta/recipes-support/libpcre/libpcre2_10.48.bb b/meta/recipes-support/libpcre/libpcre2_10.49.bb
>> similarity index 96%
>> rename from meta/recipes-support/libpcre/libpcre2_10.48.bb
>> rename to meta/recipes-support/libpcre/libpcre2_10.49.bb
>> index 56791171c238..5fa7c3db3b4c 100644
>> --- a/meta/recipes-support/libpcre/libpcre2_10.48.bb
>> +++ b/meta/recipes-support/libpcre/libpcre2_10.49.bb
>> @@ -20,7 +20,7 @@ SRC_URI = "${GITHUB_BASE_URI}/download/pcre2-${PV}/pcre2-${PV}.tar.bz2 \
>> GITHUB_BASE_URI = "https://github.com/PCRE2Project/pcre2/releases"
>> UPSTREAM_CHECK_REGEX = "releases/tag/pcre2-(?P<pver>\d+(\.\d+)+)$"
>>
>> -SRC_URI[sha256sum] = "b6c68fdf6f3ac31388b50aa89ff0fc49c00c987c16e7b5146491d12003f2c8ed"
>> +SRC_URI[sha256sum] = "53c156e1ba416a20da8e65395daa132da0d80e76910424caca3fcdae7831d384"
>>
>> CVE_PRODUCT = "pcre2"
>>
>
> Hello,
>
> Shouldn't this patch have removed
> meta/recipes-support/libpcre/libpcre2/testoutput3C ?
>
> See: https://git.openembedded.org/openembedded-core/commit/?id=3c447001749427b151dc2e6f08c790bac77b1c43
>
> Regards,
Hi,
I assumed it had to stay for this release, but my tests are proving me
wrong. I will send a patch to remove it.
Thanks,
Mathieu
--
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2026-10-05 15:34 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-30 8:16 [PATCH 00/24] 2026-09-29 upgrades Mathieu Dubois-Briand
2026-09-30 8:16 ` [PATCH 01/24] python3-pytz: upgrade 2026.3.post1 -> 2026.4 Mathieu Dubois-Briand
2026-09-30 8:16 ` [PATCH 02/24] python3-vcs-versioning: upgrade 2.4.0 -> 2.5.0 Mathieu Dubois-Briand
2026-09-30 8:16 ` [PATCH 03/24] python3-setuptools-scm: upgrade 10.2.3 -> 10.3.4 Mathieu Dubois-Briand
2026-09-30 8:16 ` [PATCH 04/24] python3-wcwidth: upgrade 0.8.3 -> 0.9.1 Mathieu Dubois-Briand
2026-09-30 8:16 ` [PATCH 05/24] gnupg: upgrade 2.5.22 -> 2.5.24 Mathieu Dubois-Briand
2026-09-30 8:16 ` [PATCH 06/24] repo: upgrade 2.67 -> 2.68.1 Mathieu Dubois-Briand
2026-09-30 8:16 ` [PATCH 07/24] python3-pbr: upgrade 7.1.0 -> 7.1.2 Mathieu Dubois-Briand
2026-09-30 8:16 ` [PATCH 08/24] ccache: upgrade 4.14 -> 4.14.1 Mathieu Dubois-Briand
2026-09-30 8:16 ` [PATCH 09/24] python3-hypothesis: upgrade 6.168.1 -> 6.168.2 Mathieu Dubois-Briand
2026-09-30 8:16 ` [PATCH 10/24] git: upgrade 2.55.0 -> 2.56.0 Mathieu Dubois-Briand
2026-09-30 8:16 ` [PATCH 11/24] spirv-headers: upgrade 1.4.357.0 -> 1.4.363.0 Mathieu Dubois-Briand
2026-09-30 8:16 ` [PATCH 12/24] vulkan-headers: " Mathieu Dubois-Briand
2026-09-30 8:16 ` [PATCH 13/24] glslang: " Mathieu Dubois-Briand
2026-09-30 8:16 ` [PATCH 14/24] spirv-tools: " Mathieu Dubois-Briand
2026-09-30 8:16 ` [PATCH 15/24] vulkan-loader: " Mathieu Dubois-Briand
2026-09-30 8:16 ` [PATCH 16/24] vulkan-tools: upgrade " Mathieu Dubois-Briand
2026-09-30 8:16 ` [PATCH 17/24] vulkan-utility-libraries: " Mathieu Dubois-Briand
2026-09-30 8:16 ` [PATCH 18/24] vulkan-validation-layers: " Mathieu Dubois-Briand
2026-09-30 8:16 ` [PATCH 19/24] vulkan-volk: " Mathieu Dubois-Briand
2026-09-30 8:16 ` [PATCH 20/24] python3-uv-build: upgrade 0.12.19 -> 0.12.20 Mathieu Dubois-Briand
2026-09-30 8:16 ` [PATCH 21/24] diffoscope: upgrade 331 -> 332 Mathieu Dubois-Briand
2026-09-30 8:16 ` [PATCH 22/24] libpcre2: upgrade 10.48 -> 10.49 Mathieu Dubois-Briand
2026-10-05 9:06 ` [OE-core] " Yoann Congal
2026-10-05 15:34 ` Mathieu Dubois-Briand [this message]
2026-09-30 8:16 ` [PATCH 23/24] igt-gpu-tools: upgrade 2.5 -> 2.6 Mathieu Dubois-Briand
2026-09-30 8:16 ` [PATCH 24/24] appstream: upgrade 1.2.0 -> 1.2.1 Mathieu Dubois-Briand
[not found] ` <18DA0B4B51CDCF67.1580077@lists.openembedded.org>
2026-09-30 11:36 ` [OE-core] [PATCH 14/24] spirv-tools: upgrade 1.4.357.0 -> 1.4.363.0 Mathieu Dubois-Briand
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=DLX0IZJ8VAS9.334U1B5L5ZG53@bootlin.com \
--to=mathieu.dubois-briand@bootlin.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=thomas.petazzoni@bootlin.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox