From: "Benjamin Robin (Schneider Electric)" <benjamin.robin@bootlin.com>
To: openembedded-core@lists.openembedded.org
Cc: ross.burton@arm.com, thomas.petazzoni@bootlin.com,
mathieu.dubois-briand@bootlin.com, antonin.godard@bootlin.com,
jpewhacker@gmail.com,
"Benjamin Robin (Schneider Electric)"
<benjamin.robin@bootlin.com>,
Peter Marko <peter.marko@siemens.com>
Subject: [PATCH 2/2] meta: in lz4 remove reference to rejected CVE-2025-62813
Date: Fri, 20 Feb 2026 12:01:57 +0100 [thread overview]
Message-ID: <20260220-update-patch-with-rejected-cve-v1-2-cf113d8a15ca@bootlin.com> (raw)
In-Reply-To: <20260220-update-patch-with-rejected-cve-v1-0-cf113d8a15ca@bootlin.com>
The CVE-2025-62813 is rejected so do not reference it anymore.
So keep the patch but without referencing the CVE identifier.
The CVE database indicates the following reason:
This candidate was withdrawn by its CNA. Further investigation
showed that it was not a security issue.
Signed-off-by: Benjamin Robin (Schneider Electric) <benjamin.robin@bootlin.com>
---
.../lz4/lz4/{CVE-2025-62813.patch => fix-null-error-handling.patch} | 1 -
meta/recipes-support/lz4/lz4_1.10.0.bb | 2 +-
2 files changed, 1 insertion(+), 2 deletions(-)
diff --git a/meta/recipes-support/lz4/lz4/CVE-2025-62813.patch b/meta/recipes-support/lz4/lz4/fix-null-error-handling.patch
similarity index 99%
rename from meta/recipes-support/lz4/lz4/CVE-2025-62813.patch
rename to meta/recipes-support/lz4/lz4/fix-null-error-handling.patch
index 4fa0373ff778..1527cc759124 100644
--- a/meta/recipes-support/lz4/lz4/CVE-2025-62813.patch
+++ b/meta/recipes-support/lz4/lz4/fix-null-error-handling.patch
@@ -4,7 +4,6 @@ Date: Mon, 31 Mar 2025 20:48:52 +0200
Subject: [PATCH] fix(null) : improve error handlings when passing a null
pointer to some functions from lz4frame
-CVE: CVE-2025-62813
Upstream-Status: Backport [https://github.com/lz4/lz4/commit/f64efec011c058bd70348576438abac222fe6c82]
Signed-off-by: Peter Marko <peter.marko@siemens.com>
---
diff --git a/meta/recipes-support/lz4/lz4_1.10.0.bb b/meta/recipes-support/lz4/lz4_1.10.0.bb
index f2a86036b56a..fae5796c2b9a 100644
--- a/meta/recipes-support/lz4/lz4_1.10.0.bb
+++ b/meta/recipes-support/lz4/lz4_1.10.0.bb
@@ -15,7 +15,7 @@ SRCREV = "ebb370ca83af193212df4dcbadcc5d87bc0de2f0"
SRC_URI = "git://github.com/lz4/lz4.git;branch=release;protocol=https \
file://reproducibility.patch \
file://run-ptest \
- file://CVE-2025-62813.patch \
+ file://fix-null-error-handling.patch \
"
UPSTREAM_CHECK_GITTAGREGEX = "v(?P<pver>.*)"
--
2.52.0
next prev parent reply other threads:[~2026-02-20 11:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-20 11:01 [PATCH 0/2] meta: remove reference in patches to rejected CVE Benjamin Robin (Schneider Electric)
2026-02-20 11:01 ` [PATCH 1/2] meta: update avahi patch to remove ref " Benjamin Robin (Schneider Electric)
2026-02-20 15:46 ` [OE-core] " Peter Kjellerstedt
2026-02-20 15:50 ` Benjamin ROBIN
2026-02-20 11:01 ` Benjamin Robin (Schneider Electric) [this message]
2026-02-20 15:47 ` [OE-core] [PATCH 2/2] meta: in lz4 remove reference to rejected CVE-2025-62813 Peter Kjellerstedt
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=20260220-update-patch-with-rejected-cve-v1-2-cf113d8a15ca@bootlin.com \
--to=benjamin.robin@bootlin.com \
--cc=antonin.godard@bootlin.com \
--cc=jpewhacker@gmail.com \
--cc=mathieu.dubois-briand@bootlin.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=peter.marko@siemens.com \
--cc=ross.burton@arm.com \
--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