issue处理注意事项:
1. 提交正常修复分支的修复PR时,必须关联当前issue,否则无法关闭当前issue;
2. 模板内容需要填写完整, 无论是受影响或者不受影响都需要填写完整内容;
3. 以下为模板中需要填写完整的内容, 请复制到评论区回复;
注: 内容的关键词(影响性分析说明, openEuler评分, 受影响版本排查(受影响/不受影响), 修复是否涉及abi变化(是/否), 原因说明)不能省略,省略后cve-manager将无法正常解析填写内容.
影响性分析说明:
openEuler评分: (评分和向量)
受影响版本排查(受影响/不受影响):
1.master(1.5.0):
2.openEuler-20.03-LTS-SP4(1.2.0):
3.openEuler-22.03-LTS-SP4(1.3.1):
4.openEuler-24.03-LTS-Next(1.4.0):
5.openEuler-24.03-LTS-SP1(1.4.0):
6.openEuler-24.03-LTS-SP3(1.4.0):
7.openEuler-24.03-LTS-SP4(1.4.0):
修复是否涉及abi变化(是/否)：
1.master(1.5.0):
2.openEuler-20.03-LTS-SP4(1.2.0):
3.openEuler-22.03-LTS-SP4(1.3.1):
4.openEuler-24.03-LTS-Next(1.4.0):
5.openEuler-24.03-LTS-SP1(1.4.0):
6.openEuler-24.03-LTS-SP3(1.4.0):
7.openEuler-24.03-LTS-SP4(1.4.0):
原因说明：
1.master(1.5.0):
2.openEuler-20.03-LTS-SP4(1.2.0):
3.openEuler-22.03-LTS-SP4(1.3.1):
4.openEuler-24.03-LTS-Next(1.4.0):
5.openEuler-24.03-LTS-SP1(1.4.0):
6.openEuler-24.03-LTS-SP3(1.4.0):
7.openEuler-24.03-LTS-SP4(1.4.0):
原因说明填写请参考下方表格(注意：版本是否受影响和版本的原因说明必须对应，例如master版本分支受影响，那原因说明只能是受影响对应的原因之一!)：
分支状态 |
原因说明 | 使用场景 |
|---|---|---|
| 受影响 | 正常修复 | 受影响且需要修复（包含升级版本修复）的漏洞； 受影响且已经修复的漏洞（历史修复PR也需要关联issue）； 若因特殊原因无法修复，应修改原因说明为【不修复-特殊原因】，并在安委会备案相关情况。 |
| 受影响 | 漏洞仍在分析中 | 已关注到相关漏洞，正在处理，未明确漏洞影响和修复方案。 |
| 受影响 | 暂不修复-暂无解决方案或补丁 | 当前没有可用的修复或补救措施。【影响性分析】中应包含有关为什么没有修复或补救措施的详细说明、上游相关PR等。 |
| 受影响 | 不修复-超出修复范围 | 没有漏洞的修复计划。当版本停维、软件包宣布生命周期终止或弃用使用。 |
| 受影响 | 不修复-特殊原因导致不再修复 | 如存在其他特殊情况不修复相关漏洞，或评估后无法升级修复，应在openEuler社区安全委员会例会进行说明备案。 【影响性分析】中应包含不发布修复的详细说明、特殊情况还应有安委会会议纪要。 |
| 不受影响 | 不受影响-组件不存在 | 软件不受影响，因为易受攻击的组件不在产品中。 |
| 不受影响 | 不受影响-已有内置的内联控制或缓解措施 | 内置的内联控制或缓解措施可防止攻击者利用漏洞 |
| 不受影响 | 不受影响-漏洞代码不能被攻击者触发 | 易受攻击的组件存在，并且该组件包含易受攻击的代码。但是，易受攻击的代码的使用方式使得攻击者无法进行任何预期的攻击。 |
| 不受影响 | 不受影响-漏洞代码不在执行路径 | 易受影响的代码在执行过程中不可访问，包括产品的非预期状态。产品不使用也不执行的组件。 |
| 不受影响 | 不受影响-漏洞代码不存在 | 产品不受影响，因为漏洞背后的代码在产品中不存在。与component_not_present不同的是，有问题的组件存在，但由于某种原因（例如安全的编译器选项）使漏洞的特定代码不存在于组件中。 |
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
| 参考网址 | 关联pr | 状态 | 补丁链接 |
|---|---|---|---|
| https://www.opencve.io/cve/CVE-2026-71225 | |||
| https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2026-71225 | |||
| https://security-tracker.debian.org/tracker/CVE-2026-71225 | |||
| http://www.cnnvd.org.cn/web/vulnerability/queryLds.tag?qcvCnnvdid=CVE-2026-71225 | |||
| https://nvd.nist.gov/vuln/detail/CVE-2026-71225 | |||
| https://ubuntu.com/security/CVE-2026-71225 | None | None | https://discourse.ubuntu.com/c/project |
说明：补丁链接仅供初步排查参考，实际可用性请人工再次确认，补丁下载验证可使用CVE补丁工具。
若补丁不准确，烦请在此issue下评论 '/report-patch 参考网址 补丁链接1,补丁链接2' 反馈正确信息，便于我们不断优化工具，不胜感激。
如 /report-patch https://security-tracker.debian.org/tracker/CVE-2021-3997 https://github.com/systemd/systemd/commit/5b1cf7a9be37e20133c0208005274ce4a5b5c6a1
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.
Contact Guide
If you have any questions, please contact the SIG: Base-service ,
and any of the maintainers: @dillon_chen, @licihua, @overweight, @shenyangyang, @xujing99, @zhujianwei001 ,
and any of the committers: @houmingyong, @jiayi0118, @qq_28851361 .
影响性分析说明：When performing one-shot symmetric cipher operations on large inputs (over 64 KiB) in stateful modes such as Counter (CTR) or Cipher Block Chaining (CBC), the library improperly reuses the Initialization Vector (IV) for each internal data chunk. A remote attacker could potentially exploit this by making an application that uses libkcapi process specially crafted large inputs. This can lead to a significant weakening of data confidentiality, as the repeated IV use can expose relationships in encrypted plaintext, and may also affect data integrity by causing incorrect cryptographic processing.
openEuler评分：6.5 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N
受影响版本排查(受影响/不受影响)：
1.master(1.5.0):受影响
2.openEuler-20.03-LTS-SP4(1.2.0):受影响
3.openEuler-22.03-LTS-SP4(1.3.1):受影响
4.openEuler-24.03-LTS-Next(1.4.0):受影响
5.openEuler-24.03-LTS-SP1(1.4.0):受影响
6.openEuler-24.03-LTS-SP3(1.4.0):受影响
7.openEuler-24.03-LTS-SP4(1.4.0):受影响
修复是否涉及abi变化(是/否)：
1.master(1.5.0):否
2.openEuler-20.03-LTS-SP4(1.2.0):否
3.openEuler-22.03-LTS-SP4(1.3.1):否
4.openEuler-24.03-LTS-Next(1.4.0):否
5.openEuler-24.03-LTS-SP1(1.4.0):否
6.openEuler-24.03-LTS-SP3(1.4.0):否
7.openEuler-24.03-LTS-SP4(1.4.0):否
原因说明：
1.master(1.5.0):正常修复
2.openEuler-20.03-LTS-SP4(1.2.0):正常修复
3.openEuler-22.03-LTS-SP4(1.3.1):正常修复
4.openEuler-24.03-LTS-Next(1.4.0):正常修复
5.openEuler-24.03-LTS-SP1(1.4.0):正常修复
6.openEuler-24.03-LTS-SP3(1.4.0):正常修复
7.openEuler-24.03-LTS-SP4(1.4.0):正常修复
@jiayi0118 经过 cve-manager 解析, 已分析的内容如下表所示:
| 状态 | 分析项目 | 内容 |
|---|---|---|
| 已分析 | 1.影响性分析说明 | When performing one-shot symmetric cipher operations on large inputs (over 64 KiB) in stateful modes such as Counter (CTR) or Cipher Block Chaining (CBC), the library improperly reuses the Initialization Vector (IV) for each internal data chunk. A remote attacker could potentially exploit this by making an application that uses libkcapi process specially crafted large inputs. This can lead to a significant weakening of data confidentiality, as the repeated IV use can expose relationships in encrypted plaintext, and may also affect data integrity by causing incorrect cryptographic processing. |
| 已分析 | 2.openEulerScore | 6.5 |
| 已分析 | 3.openEulerVector | AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N |
| 已分析 | 4.受影响版本排查 | master:受影响,openEuler-20.03-LTS-SP4:受影响,openEuler-22.03-LTS-SP4:受影响,openEuler-24.03-LTS-Next:受影响,openEuler-24.03-LTS-SP1:受影响,openEuler-24.03-LTS-SP3:受影响,openEuler-24.03-LTS-SP4:受影响 |
| 已分析 | 5.是否涉及abi变化 | master:否,openEuler-20.03-LTS-SP4:否,openEuler-22.03-LTS-SP4:否,openEuler-24.03-LTS-Next:否,openEuler-24.03-LTS-SP1:否,openEuler-24.03-LTS-SP3:否,openEuler-24.03-LTS-SP4:否 |
| 已分析 | 6.原因说明 | master:正常修复,openEuler-20.03-LTS-SP4:正常修复,openEuler-22.03-LTS-SP4:正常修复,openEuler-24.03-LTS-Next:正常修复,openEuler-24.03-LTS-SP1:正常修复,openEuler-24.03-LTS-SP3:正常修复,openEuler-24.03-LTS-SP4:正常修复 |
请确认分析内容的准确性, 确认无误后, 您可以进行后续步骤, 否则您可以继续分析.
经过cve-manager解析，部分分支PR未合入，如红色字体所示：
原因说明：
1.master:正常修复
2.openEuler-20.03-LTS-SP4:正常修复(PR未合入)
3.openEuler-22.03-LTS-SP4:正常修复(PR未合入)
4.openEuler-24.03-LTS-Next:正常修复(PR未合入)
5.openEuler-24.03-LTS-SP1:正常修复(PR未合入)
6.openEuler-24.03-LTS-SP3:正常修复(PR未合入)
7.openEuler-24.03-LTS-SP4:正常修复(PR未合入)
/branches openEuler-20.03-LTS-SP4 openEuler-22.03-LTS-SP4 /patch_url https://github.com/smuellerDD/libkcapi/commit/017adba8f54f36f92e1919687fb67a89c4d299c6
CVE-2026-71225
是否需要修复：是
是否存在适配：是
上游社区补丁：无
分支修复情况：
1.openEuler-22.03-LTS-SP4(1.3.1): 已修复
PR：
- openEuler-22.03-LTS-SP4: https://gitcode.com/src-openeuler/libkcapi/merge_requests/99
补丁适配报告 (CVE-2026-71225)
1. backport-CVE-2026-71225-1.patch
- 状态: 适配成功 (status=adapted)
- 置信度: high
- 冲突说明: Both hunks required context-only adaptation (cross-version 1.5.1-prerelease -> 1.3.1). Hunk1 (CHANGES.md, non-critical changelog): baseline section title is 'Changes 1.3.1:' not 'Changes 1.5.1-prerelease:' and baseline lacks the 'kcapi-enc: add tag processing...' leading context line; adapted hunk to use baseline-actual context and insert new changelog entry after 'fix potential for an infinite loop'. Hunk2 (lib/kcapi-kernel-if.c, SECURITY-CRITICAL): line offset 1387->1333 (function _kcapi_cipher_crypt_chunk at baseline line 1300) and context line 'outlen -= (size_t)ret;' adapted to baseline '(uint32_t)ret;'; the added comment block + 'handle->cipher.iv = NULL;' preserved VERBATIM from original patch.
CVE-2026-71225
是否需要修复：是
是否存在适配：是
上游社区补丁：无
分支修复情况：
1.openEuler-20.03-LTS-SP4(1.2.0): 已修复
PR：
- openEuler-20.03-LTS-SP4: https://gitcode.com/src-openeuler/libkcapi/merge_requests/100
补丁适配报告 (CVE-2026-71225)
1. backport-CVE-2026-71225-1.patch
- 状态: 适配成功 (status=adapted)
- 置信度: high
- 冲突说明: Both hunks adapted for cross-version 1.5.1->1.2.0 (context-only, added logic identical to original). (1) CHANGES.md: section 'Changes 1.5.1-prerelease:'->'Changes 1.2.0'; inserted ' * add safety measure to prevent IV reuse' after ' * fix memory corruption'; hunk @@ -1,4 +1,5 @@. (2) lib/kcapi-kernel-if.c: line offset 1387->1298 (function _kcapi_cipher_crypt_chunk at line 1265 in source); context line 'outlen -= (size_t)ret;' adjusted to 'outlen -= ret;' (source 1.2.0 has no cast); hunk header 'ssize_t'->'int32_t'; 9 added lines (1 blank + 7-line comment + handle->cipher.iv = NULL;) verbatim from original. handle->cipher.iv field confirmed present in baseline at lines 133/182/193 of lib/kcapi-kernel-if.c — no infrastructure missing. Patch applied to source_dir, git apply --check exit 0, git diff --stat confirmed 2 files / 10 insertions non-empty, grep confirmed handle->cipher.iv = NULL at line 1309.
/branches openEuler-24.03-LTS-Next openEuler-24.03-LTS-SP4 /patch_url https://github.com/smuellerDD/libkcapi/commit/017adba8f54f36f92e1919687fb67a89c4d299c6
CVE-2026-71225
是否需要修复：是
是否存在适配：是
上游社区补丁：无
分支修复情况：
1.openEuler-24.03-LTS-Next(1.4.0): 已修复
PR：
- openEuler-24.03-LTS-Next: https://gitcode.com/src-openeuler/libkcapi/merge_requests/101
补丁适配报告 (CVE-2026-71225)
1. backport-CVE-2026-71225-1.patch
- 状态: 适配成功 (status=adapted)
- 置信度: high
- 冲突说明: Cross-version (1.5.1-prerelease->1.4.0) context-only adaptation; 2/2 failed hunks adapted, 0 directly-applicable. Hunk1 CHANGES.md: original context expected 'Changes 1.5.1-prerelease:' header + 'kcapi-enc: add tag processing...' line (both absent in baseline 1.4.0, grep-verified 0 matches); adapted to baseline 'Changes 1.4.0:' block, inserting '* add safety measure to prevent IV reuse' right after '* fix potential for an infinite loop' (L3). Hunk2 lib/kcapi-kernel-if.c: original context 'outlen -= (size_t)ret;' absent in baseline (0 matches), baseline uses 'outlen -= (uint32_t)ret;' (L1380); adapted context line to (uint32_t)ret and offset hunk start 1387->1378. Inserted comment + 'handle->cipher.iv = NULL;' placement identical to upstream (after outlen-=, before while-loop closing brace). No structural changes.
CVE-2026-71225
是否需要修复：是
是否存在适配：是
上游社区补丁：无
分支修复情况：
1.openEuler-24.03-LTS-SP4(1.4.0): 已修复
PR：
- openEuler-24.03-LTS-SP4: https://gitcode.com/src-openeuler/libkcapi/merge_requests/102
补丁适配报告 (CVE-2026-71225)
1. backport-CVE-2026-71225-1.patch
- 状态: 适配成功 (status=adapted)
- 置信度: high
- 冲突说明: 2 hunks adapted via pure context matching (no structural divergence). Hunk 1 (CHANGES.md): version header 'Changes 1.5.1-prerelease:' adapted to baseline 'Changes 1.4.0:', removed non-existent context line 'kcapi-enc: add tag processing...', surrounding section header 'Changes 1.5.0:' adapted to 'Changes 1.3.1:'. Hunk 2 (lib/kcapi-kernel-if.c): context type cast '(size_t)ret' adapted to baseline '(uint32_t)ret' at line 1380, hunk line numbers shifted from -1387 to -1378. Added content (comment block + handle->cipher.iv = NULL) identical to original patch in both hunks.
经过cve-manager解析，部分分支PR未合入，如红色字体所示：
原因说明：
1.master:正常修复
2.openEuler-20.03-LTS-SP4:正常修复
3.openEuler-22.03-LTS-SP4:正常修复
4.openEuler-24.03-LTS-Next:正常修复
5.openEuler-24.03-LTS-SP1:正常修复(PR未合入)
6.openEuler-24.03-LTS-SP3:正常修复(PR未合入)
7.openEuler-24.03-LTS-SP4:正常修复
一、漏洞信息
漏洞编号：CVE-2026-71225
漏洞归属组件：libkcapi
漏洞归属的版本：1.2.0,1.3.1,1.4.0,1.5.0
CVSS评分：
BaseScore：6.5 Medium
Vector：CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N
漏洞简述：
A flaw was found in libkcapi. When performing one-shot symmetric cipher operations on large inputs (over 64 KiB) in stateful modes such as Counter (CTR) or Cipher Block Chaining (CBC), the library improperly reuses the Initialization Vector (IV) for each internal data chunk. A remote attacker could potentially exploit this by making an application that uses libkcapi process specially crafted large inputs. This can lead to a significant weakening of data confidentiality, as the repeated IV use can expose relationships in encrypted plaintext, and may also affect data integrity by causing incorrect cryptographic processing.
漏洞公开时间：2026-08-05 21:24:47
漏洞创建时间：2026-08-12 02:40:36
漏洞详情参考链接：
https://nvd.nist.gov/vuln/detail/CVE-2026-71225
更多参考(点击展开)
漏洞分析指导链接：
https://atomgit.com/openeuler/cve-manager/blob/master/cve-vulner-manager/doc/md/manual.md
漏洞数据来源:
其他
漏洞补丁信息：
详情(点击展开)
无
二、漏洞分析结构反馈
影响性分析说明：
When performing one-shot symmetric cipher operations on large inputs (over 64 KiB) in stateful modes such as Counter (CTR) or Cipher Block Chaining (CBC), the library improperly reuses the Initialization Vector (IV) for each internal data chunk. A remote attacker could potentially exploit this by making an application that uses libkcapi process specially crafted large inputs. This can lead to a significant weakening of data confidentiality, as the repeated IV use can expose relationships in encrypted plaintext, and may also affect data integrity by causing incorrect cryptographic processing.
openEuler评分：
6.5
Vector：CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N
受影响版本排查(受影响/不受影响)：
1.master(1.5.1):受影响
2.openEuler-20.03-LTS-SP4(1.2.0):受影响
3.openEuler-22.03-LTS-SP4(1.3.1):受影响
4.openEuler-24.03-LTS-Next(1.4.0):受影响
5.openEuler-24.03-LTS-SP1(1.4.0):受影响
6.openEuler-24.03-LTS-SP3(1.4.0):受影响
7.openEuler-24.03-LTS-SP4(1.4.0):受影响
修复是否涉及abi变化(是/否)：
1.master(1.5.1):否
2.openEuler-20.03-LTS-SP4(1.2.0):否
3.openEuler-22.03-LTS-SP4(1.3.1):否
4.openEuler-24.03-LTS-Next(1.4.0):否
5.openEuler-24.03-LTS-SP1(1.4.0):否
6.openEuler-24.03-LTS-SP3(1.4.0):否
7.openEuler-24.03-LTS-SP4(1.4.0):否
原因说明：
1.master(1.5.1):正常修复
2.openEuler-20.03-LTS-SP4(1.2.0):正常修复
3.openEuler-22.03-LTS-SP4(1.3.1):正常修复
4.openEuler-24.03-LTS-Next(1.4.0):正常修复
5.openEuler-24.03-LTS-SP1(1.4.0):正常修复
6.openEuler-24.03-LTS-SP3(1.4.0):正常修复
7.openEuler-24.03-LTS-SP4(1.4.0):正常修复