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

影响性分析说明:

openEuler评分: (评分和向量)

受影响版本排查(受影响/不受影响):
1.master(255):
2.openEuler-20.03-LTS-SP4(243):
3.openEuler-22.03-LTS-SP4(249):
4.openEuler-24.03-LTS-Next(255):
5.openEuler-24.03-LTS-SP1(255):
6.openEuler-24.03-LTS-SP3(255):
7.openEuler-24.03-LTS-SP4(255):

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

原因说明：
1.master(255):
2.openEuler-20.03-LTS-SP4(243):
3.openEuler-22.03-LTS-SP4(249):
4.openEuler-24.03-LTS-Next(255):
5.openEuler-24.03-LTS-SP1(255):
6.openEuler-24.03-LTS-SP3(255):
7.openEuler-24.03-LTS-SP4(255):

原因说明填写请参考下方表格(注意：版本是否受影响和版本的原因说明必须对应，例如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

说明：补丁链接仅供初步排查参考，实际可用性请人工再次确认，补丁下载验证可使用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 @openeuler-ci-bot , 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: @jiayi0118, @licunlong, @protkhn, @shenyangyang, @xujing99, @yue-yuankun .

/branches master,openEuler-24.03-LTS-SP4,openEuler-22.03-LTS-SP4,openEuler-20.03-LTS-SP4 /name yixiangzhike /email yixiangzhike007@163.com

正在自动化处理任务，任务编号:TASK-gitcode__systemd-384-20260827160229-0，指定分支:master

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

正在自动化处理任务，任务编号:TASK-gitcode__systemd-384-20260827160230-1，指定分支:openEuler-24.03-LTS-SP4

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

正在自动化处理任务，任务编号:TASK-gitcode__systemd-384-20260827160230-2，指定分支:openEuler-22.03-LTS-SP4

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

正在自动化处理任务，任务编号:TASK-gitcode__systemd-384-20260827160231-3，指定分支:openEuler-20.03-LTS-SP4

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

CVE-2026-16742

是否需要修复：否（不受影响）
是否存在适配：否
上游社区补丁：无

分支修复情况：
1.openEuler-20.03-LTS-SP4(243): 不受影响

CVE-2026-16742

是否需要修复：是
是否存在适配：是
上游社区补丁：https://github.com/systemd/systemd/commit/d392d17143423e7af0cdb5bd0f64b43da8952662.patch
https://github.com/systemd/systemd/commit/a7bce5b2052bdb098ad0729768c72e1df9a86adc.patch

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

PR：

• openEuler-22.03-LTS-SP4: https://gitcode.com/src-openeuler/systemd/merge_requests/1088

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

1. backport-CVE-2026-16742-1.patch

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

适配冲突说明

适配说明

• test/units/TEST-46-HOMED.sh does not exist in systemd-249 baseline (glob returned 0 results). Baseline equivalent test/units/testsuite-46.sh uses linear script style with no testcase_*/run_testcases functions (grep returned 0 matches) — incompatible with patch's testcase_identity_groups(). Skipped as non-critical test file (test/ path, no security logic). Successful hunk src/home/homed-home.c applied as-is with only line number (1109→853) and blob hash mechanical adaptation. All referenced symbols exist in baseline: home_verify_user_record@homed-home.c:396, signed_locally@homed-home.h:89, home_set_record@homed-home.c:209, user_record_good_authentication@user-record-util.c:1209.

--- 原补丁/src/home/homed-home.c
+++ 适配补丁/src/home/homed-home.c
@@ -1,4 +1,4 @@
-@@ -1109,10 +1109,21 @@ static void home_authenticating_finish(Home *h, int ret, UserRecord *hr) {
+@@ -853,10 +853,21 @@ static void home_authenticating_finish(Home *h, int ret, UserRecord *hr) {
          }
  
          if (hr) {

--- 原补丁/test/units/TEST-46-HOMED.sh
+++ 适配补丁/test/units/TEST-46-HOMED.sh
@@ -1,23 +0,0 @@
-@@ -1109,4 +1109,22 @@ testcase_deactivate_busy() {
-     homectl remove busytest
- }
- 
-+testcase_identity_groups() {
-+    NEWPASSWORD=foobar homectl create idgrouptest --enforce-password-policy=no
-+    PASSWORD=foobar homectl activate idgrouptest
-+
-+    machinectl shell idgrouptest@ /usr/bin/bash -euxo pipefail -c "jq '.memberOf = ((.memberOf // []) + [\"systemd-journal\"] | unique) | .lastChangeUSec = ((.lastChangeUSec // 0) + 3600000000)' /home/idgrouptest/.identity > /home/idgrouptest/.identity.new && mv -f /home/idgrouptest/.identity.new /home/idgrouptest/.identity"
-+    jq -e '.memberOf | index("systemd-journal") != null' /home/idgrouptest/.identity
-+
-+    PASSWORD=foobar homectl authenticate idgrouptest
-+
-+    local groups
-+    groups="$(machinectl shell idgrouptest@ /usr/bin/groups)"
-+    (! grep -q systemd-journal <<<"$groups")
-+
-+    homectl deactivate idgrouptest ||:
-+    wait_for_state idgrouptest inactive
-+    homectl remove idgrouptest
-+}
-+
- run_testcases

CVE-2026-16742

是否需要修复：是
是否存在适配：是
上游社区补丁：https://github.com/systemd/systemd/commit/8735bb63b7902b6824f4d171bca994252eb04a71.patch
https://github.com/systemd/systemd/commit/04cba0a78da9d161c2f6426751d0460fb8193263.patch

分支修复情况：
1.master(255): 已修复

PR：

• master: https://gitcode.com/src-openeuler/systemd/merge_requests/1089

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

1. backport-CVE-2026-16742-1.patch

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

适配冲突说明

适配说明

• File renamed/moved: test/units/TEST-46-HOMED.sh -> test/units/testsuite-46.sh, adapted context accordingly (removed non-existent matchtest context, anchored on done/systemd-analyze log-level info/touch /testok)
• src/home/homed-home.c applied cleanly

--- 原补丁/src/home/homed-home.c
+++ 适配补丁/src/home/homed-home.c
@@ -1,4 +1,4 @@
-@@ -1113,10 +1113,21 @@ static void home_authenticating_finish(Home *h, int ret, UserRecord *hr) {
+@@ -1027,10 +1027,21 @@ static void home_authenticating_finish(Home *h, int ret, UserRecord *hr) {
          }
  
          if (hr) {

--- 原补丁/test/units/testsuite-46.sh
+++ 适配补丁/test/units/testsuite-46.sh
@@ -0,0 +1,18 @@
+@@ -314,6 +314,17 @@ for opt in json multiplexer output synthesize with-dropin with-nss with-varlink;
+     (! userdbctl "--$opt=foo" "--$opt=''" "--$opt=🐱")
+ done
+ 
++NEWPASSWORD=foobar homectl create idgrouptest --enforce-password-policy=no
++PASSWORD=foobar homectl activate idgrouptest
++machinectl shell idgrouptest@ /usr/bin/bash -euxo pipefail -c "jq '.memberOf = ((.memberOf // []) + [\"systemd-journal\"]) | .lastChangeUSec = ((.lastChangeUSec // 0) + 3600000000)' /home/idgrouptest/.identity > /home/idgrouptest/.identity.new && mv -f /home/idgrouptest/.identity.new /home/idgrouptest/.identity"
++jq -e '.memberOf | index("systemd-journal") != null' /home/idgrouptest/.identity
++PASSWORD=foobar homectl authenticate idgrouptest
++groups="$(machinectl shell idgrouptest@ /usr/bin/groups)"
++(! grep -q systemd-journal <<<"$groups")
++homectl deactivate idgrouptest ||:
++wait_for_state idgrouptest inactive
++homectl remove idgrouptest
++
+ systemd-analyze log-level info
+ 
+ touch /testok

--- 原补丁/test/units/TEST-46-HOMED.sh
+++ 适配补丁/test/units/TEST-46-HOMED.sh
@@ -1,18 +0,0 @@
-@@ -848,6 +848,17 @@ homectl inspect matchtest
- homectl inspect matchtest | grep "Area: quux3"
- homectl remove matchtest
- 
-+NEWPASSWORD=foobar homectl create idgrouptest --enforce-password-policy=no
-+PASSWORD=foobar homectl activate idgrouptest
-+machinectl shell idgrouptest@ /usr/bin/bash -euxo pipefail -c "jq '.memberOf = ((.memberOf // []) + [\"systemd-journal\"] | unique) | .lastChangeUSec = ((.lastChangeUSec // 0) + 3600000000)' /home/idgrouptest/.identity > /home/idgrouptest/.identity.new && mv -f /home/idgrouptest/.identity.new /home/idgrouptest/.identity"
-+jq -e '.memberOf | index("systemd-journal") != null' /home/idgrouptest/.identity
-+PASSWORD=foobar homectl authenticate idgrouptest
-+groups="$(machinectl shell idgrouptest@ /usr/bin/groups)"
-+(! grep -q systemd-journal <<<"$groups")
-+homectl deactivate idgrouptest ||:
-+wait_for_state idgrouptest inactive
-+homectl remove idgrouptest
-+
- systemd-analyze log-level info
- 
- touch /testok

需人工处理的补丁

以下补丁未能自动完成适配，需要人工介入处理，请勿视为已修复。

backport-CVE-2026-16742-2.patch

⚠️ 需人工处理：自动适配无法完成，需人工介入补丁适配。

原因：

• Patch backport-CVE-2026-16742-2 depends on user_record_self_changes_allowed() function and SD_HOMED_UPDATE_OFFLINE flag that do not exist in baseline (systemd-255). Sub A returned needs_prerequisite (over_adaptation_score=8). The patch header references 'Follow-up for 70a5db5822c8056b53d9a4a9273ad12cb5f87a92' but that commit is the initial 2019 homed service commit (15680 lines) and does NOT define user_record_self_changes_allowed. Extensive search of upstream commit 04cba0a78da9d161c2f6426751d0460fb8193263's entire src/home/ tree found the function only as call sites (homed-home.c:1010, homed-home-bus.c:456) with no definition in any .c or .h file checked (user-record-util.c/.h, home-util.c/.h, homed-home.c/.h, homed-home-bus.c/.h, homed-manager.c/.h, homed-forward.h, homework-forward.h, basic/forward.h, fundamental/forward.h all checked — no results). The function is security-critical (determines whether worker-returned identity changes are self-modifiable vs privileged) and cannot be safely inlined without knowing its correct implementation. Sub C (prerequisite discovery) could not identify the specific upstream commit that introduces user_record_self_changes_allowed — the function is used at commit 04cba0a78 but its definition was not found in any file in the upstream tree. Per skill C5 exit: Sub C found=false → needs_human_review.

是否需要修复：未知
是否存在适配：否
上游社区补丁：无

分支修复情况：
1.openEuler-24.03-LTS-SP4(255): 分析失败

影响性分析说明：systemd-homed contains a local privilege escalation bug via arbitrary system group addition to a local, logged in, homed-managed user

openEuler评分：6.7 CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H

受影响版本排查(受影响/不受影响)：
1.master(255):受影响
2.openEuler-20.03-LTS-SP4(243):不受影响
3.openEuler-22.03-LTS-SP4(249):受影响
4.openEuler-24.03-LTS-Next(255):受影响
5.openEuler-24.03-LTS-SP1(255):受影响
6.openEuler-24.03-LTS-SP3(255):受影响
7.openEuler-24.03-LTS-SP4(255):受影响

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

原因说明：
1.master(255):正常修复
2.openEuler-20.03-LTS-SP4(243):不受影响-漏洞代码不存在
3.openEuler-22.03-LTS-SP4(249):正常修复
4.openEuler-24.03-LTS-Next(255):正常修复
5.openEuler-24.03-LTS-SP1(255):正常修复
6.openEuler-24.03-LTS-SP3(255):正常修复
7.openEuler-24.03-LTS-SP4(255):正常修复

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

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

经过cve-manager解析，部分分支PR未合入，如红色字体所示：

原因说明：
1.master:正常修复(PR未合入)
2.openEuler-20.03-LTS-SP4:不受影响-漏洞代码不存在
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未合入)

/check-issue

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

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

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

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