Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: ankur.tyagi85@gmail.com
To: openembedded-devel@lists.openembedded.org
Cc: Wang Mingyu <wangmy@fujitsu.com>, Khem Raj <raj.khem@gmail.com>,
	Ankur Tyagi <ankur.tyagi85@gmail.com>
Subject: [oe][meta-oe][scarthgap][PATCH 27/38] openjpeg: upgrade 2.5.3 -> 2.5.4
Date: Thu, 13 Nov 2025 19:19:02 +1300	[thread overview]
Message-ID: <20251113061914.3756301-27-ankur.tyagi85@gmail.com> (raw)
In-Reply-To: <20251113061914.3756301-1-ankur.tyagi85@gmail.com>

From: Wang Mingyu <wangmy@fujitsu.com>

CVE-2025-54874.patch
removed since it's included in 2.5.4

Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
(cherry picked from commit 2cc81690424b6134a05bd6f6fb612501bd3534ca)
Signed-off-by: Ankur Tyagi <ankur.tyagi85@gmail.com>
---
 .../openjpeg/openjpeg/CVE-2025-54874.patch    | 44 -------------------
 .../{openjpeg_2.5.3.bb => openjpeg_2.5.4.bb}  |  3 +-
 2 files changed, 1 insertion(+), 46 deletions(-)
 delete mode 100644 meta-oe/recipes-graphics/openjpeg/openjpeg/CVE-2025-54874.patch
 rename meta-oe/recipes-graphics/openjpeg/{openjpeg_2.5.3.bb => openjpeg_2.5.4.bb} (86%)

diff --git a/meta-oe/recipes-graphics/openjpeg/openjpeg/CVE-2025-54874.patch b/meta-oe/recipes-graphics/openjpeg/openjpeg/CVE-2025-54874.patch
deleted file mode 100644
index 187557a35c..0000000000
--- a/meta-oe/recipes-graphics/openjpeg/openjpeg/CVE-2025-54874.patch
+++ /dev/null
@@ -1,44 +0,0 @@
-From f809b80c67717c152a5ad30bf06774f00da4fd2d Mon Sep 17 00:00:00 2001
-From: Sebastian Rasmussen <sebras@gmail.com>
-Date: Thu, 16 Jan 2025 02:13:43 +0100
-Subject: [PATCH] opj_jp2_read_header: Check for error after parsing header.
-
-Consider the case where the caller has not set the p_image
-pointer to NULL before calling opj_read_header().
-
-If opj_j2k_read_header_procedure() fails while obtaining the rest
-of the marker segment when calling opj_stream_read_data() because
-the data stream is too short, then opj_j2k_read_header() will
-never have the chance to initialize p_image, leaving it
-uninitialized.
-
-opj_jp2_read_header() will check the p_image value whether
-opj_j2k_read_header() suceeded or failed. This may be detected as
-an error in valgrind or ASAN.
-
-The fix is to check whether opj_j2k_read_header() suceeded before
-using the output argument p_image.
-
-CVE: CVE-2025-54874
-Upstream-Status: Backport [https://github.com/uclouvain/openjpeg/commit/f809b80c67717c152a5ad30bf06774f00da4fd2d]
-Signed-off-by: Hitendra Prajapati <hprajapati@mvista.com>
----
- src/lib/openjp2/jp2.c | 2 +-
- 1 file changed, 1 insertion(+), 1 deletion(-)
-
-diff --git a/src/lib/openjp2/jp2.c b/src/lib/openjp2/jp2.c
-index 4df055a5..da506318 100644
---- a/src/lib/openjp2/jp2.c
-+++ b/src/lib/openjp2/jp2.c
-@@ -2873,7 +2873,7 @@ OPJ_BOOL opj_jp2_read_header(opj_stream_private_t *p_stream,
-                               p_image,
-                               p_manager);
- 
--    if (p_image && *p_image) {
-+    if (ret && p_image && *p_image) {
-         /* Set Image Color Space */
-         if (jp2->enumcs == 16) {
-             (*p_image)->color_space = OPJ_CLRSPC_SRGB;
--- 
-2.50.1
-
diff --git a/meta-oe/recipes-graphics/openjpeg/openjpeg_2.5.3.bb b/meta-oe/recipes-graphics/openjpeg/openjpeg_2.5.4.bb
similarity index 86%
rename from meta-oe/recipes-graphics/openjpeg/openjpeg_2.5.3.bb
rename to meta-oe/recipes-graphics/openjpeg/openjpeg_2.5.4.bb
index 586bfeaf1f..945abbcc35 100644
--- a/meta-oe/recipes-graphics/openjpeg/openjpeg_2.5.3.bb
+++ b/meta-oe/recipes-graphics/openjpeg/openjpeg_2.5.4.bb
@@ -7,9 +7,8 @@ DEPENDS = "libpng tiff lcms zlib"
 
 SRC_URI = "git://github.com/uclouvain/openjpeg.git;branch=master;protocol=https \
            file://0001-Do-not-ask-cmake-to-export-binaries-they-don-t-make-.patch \
-           file://CVE-2025-54874.patch \
            "
-SRCREV = "210a8a5690d0da66f02d49420d7176a21ef409dc"
+SRCREV = "6c4a29b00211eb0430fa0e5e890f1ce5c80f409f"
 S = "${WORKDIR}/git"
 
 inherit cmake


  parent reply	other threads:[~2025-11-13  6:20 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-13  6:18 [oe][meta-oe][scarthgap][PATCH 01/38] evtest: upgrade 1.35 -> 1.36 ankur.tyagi85
2025-11-13  6:18 ` [oe][meta-oe][scarthgap][PATCH 02/38] xrdp: upgrade 0.9.19 -> 0.9.20 ankur.tyagi85
2025-11-13  6:18 ` [oe][meta-oe][scarthgap][PATCH 03/38] xmlsec1: upgrade 1.3.4 -> 1.3.5 ankur.tyagi85
2025-11-13  6:18 ` [oe][meta-oe][scarthgap][PATCH 04/38] xdg-desktop-portal: update 1.18.1 -> 1.18.4 ankur.tyagi85
2025-11-13  6:18 ` [oe][meta-oe][scarthgap][PATCH 05/38] flatpak;xdg-desktop-portal: add missing runtime dependency on fuse3-utils ankur.tyagi85
2025-11-13  6:18 ` [oe][meta-oe][scarthgap][PATCH 06/38] usbids: upgrade 2023.01.16 -> 2025.04.01 ankur.tyagi85
2025-11-13  6:18 ` [oe][meta-oe][scarthgap][PATCH 07/38] usbids: upgrade 2025.04.01 -> 2025.09.15 ankur.tyagi85
2025-11-13  6:18 ` [oe][meta-oe][scarthgap][PATCH 08/38] tbb: upgrade 2021.11.0 -> 2021.12.0 ankur.tyagi85
2025-11-13  6:18 ` [oe][meta-oe][scarthgap][PATCH 09/38] openldap: upgrade 2.6.7 -> 2.6.8 ankur.tyagi85
2025-11-13  6:18 ` [oe][meta-oe][scarthgap][PATCH 10/38] openldap: upgrade 2.6.8 -> 2.6.9 ankur.tyagi85
2025-11-13  6:18 ` [oe][meta-oe][scarthgap][PATCH 11/38] openldap: make license match spdx identifier ankur.tyagi85
2025-11-13  6:18 ` [oe][meta-oe][scarthgap][PATCH 12/38] openldap: upgrade 2.6.9 -> 2.6.10 ankur.tyagi85
2025-11-13  6:18 ` [oe][meta-oe][scarthgap][PATCH 13/38] mcelog: upgrade 198 -> 199 ankur.tyagi85
2025-11-13  6:18 ` [oe][meta-oe][scarthgap][PATCH 14/38] mcelog: upgrade 199 -> 200 ankur.tyagi85
2025-11-13  6:18 ` [oe][meta-oe][scarthgap][PATCH 15/38] libiodbc: upgrade 3.52.15 -> 3.52.16 ankur.tyagi85
2025-11-13  6:18 ` [oe][meta-oe][scarthgap][PATCH 16/38] libgpiod: update to v1.6.5 ankur.tyagi85
2025-11-13  6:18 ` [oe][meta-oe][scarthgap][PATCH 17/38] libgpiod: update v2.1.2 -> v2.1.3 ankur.tyagi85
2025-11-13  6:18 ` [oe][meta-oe][scarthgap][PATCH 18/38] libbytesize: upgrade 2.10 -> 2.11 ankur.tyagi85
2025-11-13  6:18 ` [oe][meta-oe][scarthgap][PATCH 19/38] audit: upgrade 4.0.1 -> 4.0.2 ankur.tyagi85
2025-11-13  6:18 ` [oe][meta-oe][scarthgap][PATCH 20/38] audit: Fix CVE_PRODUCT ankur.tyagi85
2025-11-13  6:18 ` [oe][meta-oe][scarthgap][PATCH 21/38] audit: fix build when systemd is enabled ankur.tyagi85
2025-11-13  6:18 ` [oe][meta-oe][scarthgap][PATCH 22/38] libbpf: upgrade 1.4.0 -> 1.4.2 ankur.tyagi85
2025-11-13  6:18 ` [oe][meta-oe][scarthgap][PATCH 23/38] libbpf: upgrade 1.4.2 -> 1.4.3 ankur.tyagi85
2025-11-13  6:18 ` [oe][meta-oe][scarthgap][PATCH 24/38] libbpf: upgrade 1.4.3 -> 1.4.5 ankur.tyagi85
2025-11-13  6:19 ` [oe][meta-oe][scarthgap][PATCH 25/38] libbpf: upgrade 1.4.5 -> 1.4.6 ankur.tyagi85
2025-11-13  6:19 ` [oe][meta-oe][scarthgap][PATCH 26/38] libbpf: upgrade 1.4.6 -> 1.4.7 ankur.tyagi85
2025-11-13  6:19 ` ankur.tyagi85 [this message]
2025-11-13  6:19 ` [oe][meta-oe][scarthgap][PATCH 28/38] neatvnc: upgrade 0.8.0 -> 0.8.1 ankur.tyagi85
2025-11-13  6:19 ` [oe][meta-oe][scarthgap][PATCH 29/38] jasper: upgrade 4.1.1 -> 4.1.2 ankur.tyagi85
2025-11-13  6:19 ` [oe][meta-oe][scarthgap][PATCH 30/38] libspiro: upgrade 20221101 -> 20230902 ankur.tyagi85
2025-11-13  6:19 ` [oe][meta-oe][scarthgap][PATCH 31/38] feh: upgrade 3.10.2 -> 3.10.3 ankur.tyagi85
2025-11-13  6:19 ` [oe][meta-oe][scarthgap][PATCH 32/38] redis-plus-plus: upgrade 1.3.11 -> 1.3.12 ankur.tyagi85
2025-11-13  6:19 ` [oe][meta-oe][scarthgap][PATCH 33/38] redis: upgrade 7.2.11 -> 7.2.12 ankur.tyagi85
2025-11-13  6:19 ` [oe][meta-oe][scarthgap][PATCH 34/38] redis: upgrade 6.2.20 -> 6.2.21 ankur.tyagi85
2025-11-13  6:19 ` [oe][meta-oe][scarthgap][PATCH 35/38] cryptsetup: upgrade 2.7.2 -> 2.7.3 ankur.tyagi85
2025-11-13  6:19 ` [oe][meta-oe][scarthgap][PATCH 36/38] cryptsetup: upgrade 2.7.3 -> 2.7.4 ankur.tyagi85
2025-11-13  6:19 ` [oe][meta-oe][scarthgap][PATCH 37/38] cryptsetup: upgrade 2.7.4 -> 2.7.5 ankur.tyagi85
2025-11-13  6:19 ` [oe][meta-oe][scarthgap][PATCH 38/38] botan: patch CVE-2024-34703 ankur.tyagi85

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=20251113061914.3756301-27-ankur.tyagi85@gmail.com \
    --to=ankur.tyagi85@gmail.com \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=raj.khem@gmail.com \
    --cc=wangmy@fujitsu.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