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

影响性分析说明:

openEuler评分: (评分和向量)

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

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

原因说明：
1.master(2.40.4):
2.openEuler-20.03-LTS-SP4(2.35.2):
3.openEuler-22.03-LTS-SP4(2.37.2):
4.openEuler-24.03-LTS-Next(2.39.1):
5.openEuler-24.03-LTS-SP1(2.39.1):
6.openEuler-24.03-LTS-SP3(2.39.1):
7.openEuler-24.03-LTS-SP4(2.39.1):

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

说明：补丁链接仅供初步排查参考，实际可用性请人工再次确认，补丁下载验证可使用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 master /patch_url https://github.com/util-linux/util-linux/commit/a15c00a9e545aa8b9cf6ec0f888ff6c7b3eaeedc /name yixiangzhike /email yixiangzhike007@163.com

正在自动化处理任务，任务编号:TASK-gitcode__util-linux-172-20260904153750，指定分支:master，使用指定补丁(1个)

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

CVE-2026-76642

是否需要修复：是
是否存在适配：是
上游社区补丁：https://github.com/util-linux/util-linux/commit/a15c00a9e545aa8b9cf6ec0f888ff6c7b3eaeedc

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

PR：

• master: https://gitcode.com/src-openeuler/util-linux/merge_requests/553

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

1. backport-CVE-2026-76642.patch

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

适配冲突说明

适配说明

• Hunk 3 of libmount/src/context_mount.c failed to apply: baseline 2.40.4 has an extra 1-tab closing brace (line 1059) after the 2-tab brace that the upstream patch context omits. The core change (if (rc == 0) -> if (rc == 0 && !is_mount_stage_failed(cxt))) is byte-identical. Adaptation = replace context line ('goto again
• ' -> '\t}') to match baseline, renumber hunk header @@ -1107,7 +1124,7 @@ -> @@ -1058,7 +1075,7 @@. Hunks 1, 2, 4, 5 apply cleanly with line number offsets only.

--- 原补丁/libmount/src/context_mount.c
+++ 适配补丁/libmount/src/context_mount.c
@@ -1,4 +1,4 @@
-@@ -582,6 +582,22 @@ static int is_success_status(struct libmnt_context *cxt)
+@@ -575,6 +575,22 @@ static int is_success_status(struct libmnt_context *cxt)
  	return 0;
  }
  
@@ -21,7 +21,7 @@
  static int is_termination_status(struct libmnt_context *cxt)
  {
  	if (is_success_status(cxt))
-@@ -888,8 +904,9 @@ int mnt_context_do_mount(struct libmnt_context *cxt)
+@@ -874,8 +890,9 @@ int mnt_context_do_mount(struct libmnt_context *cxt)
  	} else
  		res = do_mount_by_pattern(cxt, cxt->fstype_pattern);
  
@@ -33,8 +33,8 @@
  		rc = mnt_context_call_hooks(cxt, MNT_STAGE_MOUNT_POST);
  		if (rc)
  			return rc;
-@@ -1107,7 +1124,7 @@ int mnt_context_mount(struct libmnt_context *cxt)
- 			goto again;
+@@ -1058,7 +1075,7 @@ again:
+ 		}
  	}
  
 -	if (rc == 0)

影响性分析说明：util-linux versions through 2.41.5 and 2.42.2 fail to check mount helper exit status before running post-mount hooks, allowing unprivileged users to execute privileged operations on pre-existing filesystems. Attackers can exploit X-mount.idmap or X-mount.owner hooks to clone filesystems with inherited suid bits or modify target inode permissions after a helper fails, achieving privilege escalation.

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

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

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

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

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

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

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

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

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