issue处理注意事项:
1. 提交正常修复分支的修复PR时,必须关联当前issue,否则无法关闭当前issue;
2. 模板内容需要填写完整, 无论是受影响或者不受影响都需要填写完整内容;
3. 以下为模板中需要填写完整的内容, 请复制到评论区回复;
注: 内容的关键词(影响性分析说明, openEuler评分, 受影响版本排查(受影响/不受影响), 修复是否涉及abi变化(是/否), 原因说明)不能省略,省略后cve-manager将无法正常解析填写内容.

影响性分析说明:

openEuler评分: (评分和向量)

受影响版本排查(受影响/不受影响):
1.master(3.5.6):
2.openEuler-20.03-LTS-SP4(1.1.1f):
3.openEuler-22.03-LTS-SP4(1.1.1wa):
4.openEuler-24.03-LTS-Next(3.5.6):
5.openEuler-24.03-LTS-SP1(3.0.12):
6.openEuler-24.03-LTS-SP3(3.0.12):
7.openEuler-24.03-LTS-SP4(3.5.6):

修复是否涉及abi变化(是/否)：
1.master(3.5.6):
2.openEuler-20.03-LTS-SP4(1.1.1f):
3.openEuler-22.03-LTS-SP4(1.1.1wa):
4.openEuler-24.03-LTS-Next(3.5.6):
5.openEuler-24.03-LTS-SP1(3.0.12):
6.openEuler-24.03-LTS-SP3(3.0.12):
7.openEuler-24.03-LTS-SP4(3.5.6):

原因说明：
1.master(3.5.6):
2.openEuler-20.03-LTS-SP4(1.1.1f):
3.openEuler-22.03-LTS-SP4(1.1.1wa):
4.openEuler-24.03-LTS-Next(3.5.6):
5.openEuler-24.03-LTS-SP1(3.0.12):
6.openEuler-24.03-LTS-SP3(3.0.12):
7.openEuler-24.03-LTS-SP4(3.5.6):

原因说明填写请参考下方表格(注意：版本是否受影响和版本的原因说明必须对应，例如master版本分支受影响，那原因说明只能是受影响对应的原因之一!)：

issue处理具体操作请参考:
https://atomgit.com/openeuler/cve-manager/blob/master/cve-vulner-manager/doc/md/manual.md
pr关联issue具体操作请参考:
https://docs.atomgit.com/docs/help/home/org_project/pullrequests/pr-related-issue

Welcome To openEuler Community

Hey @openLiBingCI , thanks for your contribution to the community.

Bot Usage Manual

I'm the Bot here serving you. You can find the instructions on how to interact with me at Here . That means you can comment below every pull request or issue to trigger Bot Commands. You can self-configure the PR merge rules for this repository. For more details, please refer to Here.

Contact Guide

If you have any questions, please contact the SIG: sig-security-facility ,
and any of the maintainers: @mailofzxf, @robertosassu, @zhujianwei001 ,
and any of the committers: @gcw_n2PeTU3z, @zcfsite .

说明：补丁链接仅供初步排查参考，实际可用性请人工再次确认，补丁下载验证可使用CVE补丁工具。
若补丁不准确，烦请在此issue下评论 '/report-patch 参考网址 补丁链接1,补丁链接2' 反馈正确信息，便于我们不断优化工具，不胜感激。
如 /report-patch https://security-tracker.debian.org/tracker/CVE-2021-3997 https://github.com/systemd/systemd/commit/5b1cf7a9be37e20133c0208005274ce4a5b5c6a1

/branches openEuler-22.03-LTS-SP4 /name fly_fzc /email 2385803914@qq.com

正在自动化处理任务，任务编号:TASK-gitcode__openssl-281-20260827104209，指定分支:openEuler-22.03-LTS-SP4

✅ 任务结束 (用时: 26分钟)

CVE-2026-54874

是否需要修复：是
是否存在适配：是
上游社区补丁：https://github.com/openssl/openssl/commit/4808b5d64176451f3d93d87d0ac9c81a9b13fb23.patch
https://github.com/openssl/openssl/commit/7110cb2f75806d0bf809eb2f90790d477900be40.patch
https://github.com/openssl/openssl/commit/a0c8ec557d9cac078f032d76cdf684fe743eb382.patch
https://github.com/openssl/openssl/commit/cc0c6710917cd5eec001b297355d2ba723505107.patch
https://github.com/openssl/openssl/commit/f52ffc11b90737ac89083909618dc2e1f42c561c.patch

分支修复情况：
1.openEuler-22.03-LTS-SP4(1.1.1wa): 已修复

PR：

• openEuler-22.03-LTS-SP4: https://gitcode.com/src-openeuler/openssl/merge_requests/680

补丁适配报告 (CVE-2026-54874)

1. backport-CVE-2026-54874-3.patch

• 状态: 适配成功 (status=adapted)
• 置信度: high

适配冲突说明

适配说明

• 2/2 hunks context-adapted for openssl-1.1.1wa baseline. Baseline lacks 'size_t out_alloc_len = 0
• ' declaration and 'out_alloc_len = (size_t)outlen
• ' assignment (present in upstream patch context but absent in 1.1.1wa). Baseline uses 'EVP_CIPHER_CTX_key_length' instead of upstream's 'EVP_CIPHER_CTX_get_key_length'. Context lines adjusted to match baseline
• blank line after 'int outlen
• ' removed (baseline has none). Core security fix (size_t outsize declaration, outsize = (size_t)outlen < inlen ? inlen : (size_t)outlen computation, OPENSSL_malloc(outsize) call) is byte-identical to upstream. Patch applied to source_dir via git apply (exit 0), git diff --stat confirms 8 insertions(+), 1 deletion(-). Security fix verified present in source at lines 196, 214, 215.

--- 原补丁/crypto/cms/cms_kari.c
+++ 适配补丁/crypto/cms/cms_kari.c
@@ -1,12 +1,12 @@
-@@ -218,6 +218,7 @@ static int cms_kek_cipher(unsigned char **pout, size_t *poutlen,
+@@ -193,6 +193,7 @@ static int cms_kek_cipher(unsigned char **pout, size_t *poutlen,
+     int rv = 0;
      unsigned char *out = NULL;
-     size_t out_alloc_len = 0;
      int outlen;
 +    size_t outsize;
- 
-     keklen = EVP_CIPHER_CTX_get_key_length(kari->ctx);
+     keklen = EVP_CIPHER_CTX_key_length(kari->ctx);
      if (keklen > EVP_MAX_KEY_LENGTH)
-@@ -231,7 +232,13 @@ static int cms_kek_cipher(unsigned char **pout, size_t *poutlen,
+         return 0;
+@@ -205,7 +206,13 @@ static int cms_kek_cipher(unsigned char **pout, size_t *poutlen,
      /* obtain output length of ciphered key */
      if (!EVP_CipherUpdate(kari->ctx, NULL, &outlen, in, inlen))
          goto err;
@@ -20,4 +20,4 @@
 +    out = OPENSSL_malloc(outsize);
      if (out == NULL)
          goto err;
-     out_alloc_len = (size_t)outlen;
+     if (!EVP_CipherUpdate(kari->ctx, out, &outlen, in, inlen))

影响性分析说明:
Issue summary: Receiving a DTLS record for a future epoch while a handshake is in progress causes OpenSSL to buffer far more memory than the record itself requires. Impact summary: A peer can use a small amount of network traffic to make an OpenSSL DTLS endpoint retain a disproportionately large amount of memory, which may lead to a Denial of Service. CWE: CWE-405: Asymmetric Resource Consumption (Amplification) Description: While a DTLS handshake is in progress, a peer may legitimately have already moved on to the next epoch (for example, having sent its ChangeCipherSpec and Finished messages) before the local endpoint has processed the same transition, typically because of reordering on the underlying UDP transport. OpenSSL buffers such early records so that they can be processed once the local endpoint catches up. Buffering a record currently retains the entire read buffer it arrived in, which is sized to hold the largest possible DTLS record (around 16 kilobytes), rather than just the bytes that make up the record itself. Up to 100 such records may be buffered per connection. As a result, a peer that sends a stream of small forged records claiming to belong to the next epoch can cause an OpenSSL DTLS endpoint to retain around 1.7 megabytes of memory, despite sending only a small fraction of that amount of data over the network. An attacker therefore gains a memory amplification factor of around 1200, and can multiply the effect across as many associations as it is able to open, making this a remote memory exhaustion Denial of Service risk for DTLS servers. Since the memory retained per connection remains bounded, and any limit an application already places on the number of concurrent associations also bounds the total exposure, this issue has been assessed as Low severity. FIPS impact: no No FIPS modules are affected by this issue as the affected code is outside the OpenSSL FIPS module boundary. OpenSSL 4.0, 3.6, 3.5, 3.4, 3.0, 1.1.1 and 1.0.2 are vulnerable to this issue.

openEuler评分: (评分和向量)
BaseScore：7.5 High
Vector：CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

受影响版本排查(受影响/不受影响):
1.master(3.5.6):受影响
2.openEuler-20.03-LTS-SP4(1.1.1f):受影响
3.openEuler-22.03-LTS-SP4(1.1.1wa):受影响
4.openEuler-24.03-LTS-Next(3.5.6):受影响
5.openEuler-24.03-LTS-SP1(3.0.12):受影响
6.openEuler-24.03-LTS-SP3(3.0.12):受影响
7.openEuler-24.03-LTS-SP4(3.5.6):受影响

修复是否涉及abi变化(是/否)：
1.master(3.5.6):否
2.openEuler-20.03-LTS-SP4(1.1.1f):否
3.openEuler-22.03-LTS-SP4(1.1.1wa):否
4.openEuler-24.03-LTS-Next(3.5.6):否
5.openEuler-24.03-LTS-SP1(3.0.12):否
6.openEuler-24.03-LTS-SP3(3.0.12):否
7.openEuler-24.03-LTS-SP4(3.5.6):否

原因说明：
1.master(3.5.6):正常修复
2.openEuler-20.03-LTS-SP4(1.1.1f):正常修复
3.openEuler-22.03-LTS-SP4(1.1.1wa):正常修复
4.openEuler-24.03-LTS-Next(3.5.6):正常修复
5.openEuler-24.03-LTS-SP1(3.0.12):正常修复
6.openEuler-24.03-LTS-SP3(3.0.12):正常修复
7.openEuler-24.03-LTS-SP4(3.5.6):正常修复

@gcw_n2PeTU3z 经过 cve-manager 解析, 已分析的内容如下表所示:

请确认分析内容的准确性, 确认无误后, 您可以进行后续步骤, 否则您可以继续分析.

经过cve-manager解析，所有PR均已合入

经过cve-manager解析，所有PR均已合入