From: Wang Mingyu < wangmy@fujitsu.com>
To: openembedded-devel@lists.openembedded.org
Cc: Wang Mingyu <wangmy@fujitsu.com>
Subject: [oe] [meta-networking] [PATCH 01/29] corosync: upgrade 3.1.9 -> 3.1.10
Date: Tue, 18 Nov 2025 17:08:18 +0800 [thread overview]
Message-ID: <20251118090846.1484-1-wangmy@fujitsu.com> (raw)
From: Wang Mingyu <wangmy@fujitsu.com>
CVE-2025-30472.patch
removed since it's included in 3.1.10
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
---
.../corosync/corosync/CVE-2025-30472.patch | 69 -------------------
.../{corosync_3.1.9.bb => corosync_3.1.10.bb} | 5 +-
2 files changed, 2 insertions(+), 72 deletions(-)
delete mode 100644 meta-networking/recipes-extended/corosync/corosync/CVE-2025-30472.patch
rename meta-networking/recipes-extended/corosync/{corosync_3.1.9.bb => corosync_3.1.10.bb} (94%)
diff --git a/meta-networking/recipes-extended/corosync/corosync/CVE-2025-30472.patch b/meta-networking/recipes-extended/corosync/corosync/CVE-2025-30472.patch
deleted file mode 100644
index 9b36dbe3fb..0000000000
--- a/meta-networking/recipes-extended/corosync/corosync/CVE-2025-30472.patch
+++ /dev/null
@@ -1,69 +0,0 @@
-From 7839990f9cdf34e55435ed90109e82709032466a Mon Sep 17 00:00:00 2001
-From: Jan Friesse <jfriesse@redhat.com>
-Date: Mon, 24 Mar 2025 12:05:08 +0100
-Subject: [PATCH] totemsrp: Check size of orf_token msg
-
-orf_token message is stored into preallocated array on endian convert
-so carefully crafted malicious message can lead to crash of corosync.
-
-Solution is to check message size beforehand.
-
-Signed-off-by: Jan Friesse <jfriesse@redhat.com>
-Reviewed-by: Christine Caulfield <ccaulfie@redhat.com>
-
-CVE: CVE-2025-30472
-Upstream-Status: Backport [https://github.com/corosync/corosync/commits/7839990f9cdf34e55435ed90109e82709032466a]
-Signed-off-by: Peter Marko <peter.marko@siemens.com>
----
- exec/totemsrp.c | 18 +++++++++++++++++-
- 1 file changed, 17 insertions(+), 1 deletion(-)
-
-diff --git a/exec/totemsrp.c b/exec/totemsrp.c
-index 962d0e2a..364528ce 100644
---- a/exec/totemsrp.c
-+++ b/exec/totemsrp.c
-@@ -3679,12 +3679,20 @@ static int check_orf_token_sanity(
- const struct totemsrp_instance *instance,
- const void *msg,
- size_t msg_len,
-+ size_t max_msg_len,
- int endian_conversion_needed)
- {
- int rtr_entries;
- const struct orf_token *token = (const struct orf_token *)msg;
- size_t required_len;
-
-+ if (msg_len > max_msg_len) {
-+ log_printf (instance->totemsrp_log_level_security,
-+ "Received orf_token message is too long... ignoring.");
-+
-+ return (-1);
-+ }
-+
- if (msg_len < sizeof(struct orf_token)) {
- log_printf (instance->totemsrp_log_level_security,
- "Received orf_token message is too short... ignoring.");
-@@ -3698,6 +3706,13 @@ static int check_orf_token_sanity(
- rtr_entries = token->rtr_list_entries;
- }
-
-+ if (rtr_entries > RETRANSMIT_ENTRIES_MAX) {
-+ log_printf (instance->totemsrp_log_level_security,
-+ "Received orf_token message rtr_entries is corrupted... ignoring.");
-+
-+ return (-1);
-+ }
-+
- required_len = sizeof(struct orf_token) + rtr_entries * sizeof(struct rtr_item);
- if (msg_len < required_len) {
- log_printf (instance->totemsrp_log_level_security,
-@@ -3868,7 +3883,8 @@ static int message_handler_orf_token (
- "Time since last token %0.4f ms", tv_diff / (float)QB_TIME_NS_IN_MSEC);
- #endif
-
-- if (check_orf_token_sanity(instance, msg, msg_len, endian_conversion_needed) == -1) {
-+ if (check_orf_token_sanity(instance, msg, msg_len, sizeof(token_storage),
-+ endian_conversion_needed) == -1) {
- return (0);
- }
-
diff --git a/meta-networking/recipes-extended/corosync/corosync_3.1.9.bb b/meta-networking/recipes-extended/corosync/corosync_3.1.10.bb
similarity index 94%
rename from meta-networking/recipes-extended/corosync/corosync_3.1.9.bb
rename to meta-networking/recipes-extended/corosync/corosync_3.1.10.bb
index 1699701c9d..07d9333ec8 100644
--- a/meta-networking/recipes-extended/corosync/corosync_3.1.9.bb
+++ b/meta-networking/recipes-extended/corosync/corosync_3.1.10.bb
@@ -9,9 +9,8 @@ inherit autotools pkgconfig systemd github-releases
SRC_URI = "${GITHUB_BASE_URI}/download/v${PV}/${BP}.tar.gz \
file://corosync.conf \
- file://CVE-2025-30472.patch \
- "
-SRC_URI[sha256sum] = "203354bbddee1a97b3c50a076eae89c635f406dd674ccaefc94bb9092acd9535"
+ "
+SRC_URI[sha256sum] = "be361c827f99b215b3bd3fa2fb071c03dac6831c2a351963d938caef62604bc8"
UPSTREAM_CHECK_GITTAGREGEX = "v(?P<pver>\d+(\.\d+)+)"
LICENSE = "BSD-3-Clause"
--
2.43.0
next reply other threads:[~2025-11-18 9:08 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-18 9:08 Wang Mingyu [this message]
2025-11-18 9:08 ` [oe] [meta-oe] [PATCH 02/29] ctags: upgrade 6.2.20251109.0 -> 6.2.20251116.0 Wang Mingyu
2025-11-18 9:08 ` [oe] [meta-oe] [PATCH 03/29] drm-info: upgrade 2.8.0 -> 2.9.0 Wang Mingyu
2025-11-18 9:08 ` [oe] [meta-oe] [PATCH 04/29] freerdp3: upgrade 3.17.2 -> 3.18.0 Wang Mingyu
2025-11-18 9:08 ` [oe] [meta-oe] [PATCH 05/29] graphviz: upgrade 14.0.2 -> 14.0.4 Wang Mingyu
2025-11-18 9:08 ` [oe] [meta-networking] [PATCH 06/29] libcpr: upgrade 1.12.0 -> 1.13.0 Wang Mingyu
2025-11-18 9:08 ` [oe] [meta-oe] [PATCH 07/29] lprng: upgrade 3.8.C -> 3.9.0 Wang Mingyu
2025-11-18 9:08 ` [oe] [meta-oe] [PATCH 08/29] nano: upgrade 8.6 -> 8.7 Wang Mingyu
2025-11-18 9:08 ` [oe] [meta-networking] [PATCH 09/29] nbdkit: upgrade 1.45.12 -> 1.45.14 Wang Mingyu
2025-11-18 9:08 ` [oe] [meta-networking] [PATCH 10/29] openipmi: upgrade 2.0.36 -> 2.0.37 Wang Mingyu
2025-11-18 9:08 ` [oe] [meta-oe] [PATCH 11/29] pkcs11-helper: upgrade 1.30.0 -> 1.31.0 Wang Mingyu
2025-11-18 9:08 ` [oe] [meta-oe] [PATCH 12/29] pv: upgrade 1.10.0 -> 1.10.1 Wang Mingyu
2025-11-18 9:08 ` [oe] [meta-python] [PATCH 13/29] python3-alembic: upgrade 1.17.1 -> 1.17.2 Wang Mingyu
2025-11-18 9:08 ` [oe] [meta-python] [PATCH 14/29] python3-apiflask: upgrade 2.4.0 -> 3.0.0 Wang Mingyu
2025-11-18 9:08 ` [oe] [meta-python] [PATCH 15/29] python3-asttokens: upgrade 3.0.0 -> 3.0.1 Wang Mingyu
2025-11-18 9:08 ` [oe] [meta-python] [PATCH 16/29] python3-black: upgrade 25.9.0 -> 25.11.0 Wang Mingyu
2025-11-18 9:08 ` [oe] [meta-python] [PATCH 17/29] python3-cachetools: upgrade 6.2.1 -> 6.2.2 Wang Mingyu
2025-11-18 9:08 ` [oe] [meta-python] [PATCH 18/29] python3-cantools: upgrade 40.7.1 -> 41.0.0 Wang Mingyu
2025-11-18 9:08 ` [oe] [meta-python] [PATCH 19/29] python3-execnet: upgrade 2.1.1 -> 2.1.2 Wang Mingyu
2025-11-18 9:08 ` [oe] [meta-python] [PATCH 20/29] python3-parsimonious: upgrade 0.10.0 -> 0.11.0 Wang Mingyu
2025-11-18 9:08 ` [oe] [meta-python] [PATCH 21/29] python3-prettytable: upgrade 3.16.0 -> 3.17.0 Wang Mingyu
2025-11-18 9:08 ` [oe] [meta-python] [PATCH 22/29] python3-protobuf: upgrade 6.33.0 -> 6.33.1 Wang Mingyu
2025-11-18 9:08 ` [oe] [meta-python] [PATCH 23/29] python3-pyais: upgrade 2.13.2 -> 2.13.3 Wang Mingyu
2025-11-18 9:08 ` [oe] [meta-python] [PATCH 24/29] python3-pymongo: upgrade 4.15.3 -> 4.15.4 Wang Mingyu
2025-11-18 9:08 ` [oe] [meta-python] [PATCH 25/29] python3-snagboot: upgrade 2.4 -> 2.5 Wang Mingyu
2025-11-18 9:08 ` [oe] [meta-python] [PATCH 26/29] python3-yamlloader: upgrade 1.5.2 -> 1.6.0 Wang Mingyu
2025-11-18 9:08 ` [oe] [meta-oe] [PATCH 27/29] qcbor: upgrade 1.5.3 -> 1.6 Wang Mingyu
2025-11-18 9:08 ` [oe] [meta-oe] [PATCH 28/29] ser2net: upgrade 4.6.5 -> 4.6.6 Wang Mingyu
2025-11-18 9:08 ` [oe] [meta-filesystems] [PATCH 29/29] sshfs-fuse: upgrade 3.7.3 -> 3.7.5 Wang Mingyu
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=20251118090846.1484-1-wangmy@fujitsu.com \
--to=wangmy@fujitsu.com \
--cc=openembedded-devel@lists.openembedded.org \
/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