检测到新建 CVE Issue,CVE-ID: CVE-2026-99224。
你可以通过以下两种方式使用 CVE 修复服务:
-
分支影响分析
- 在本 Issue 下评论:
/analysis_branches - 系统将自动分析各个分支是否受影响,并在本 Issue 下给出表格形式的分析结果;
- 在本 Issue 下评论:
-
在指定分支上创建 PR(修复提交)
- 在本 Issue 下按如下格式评论(
branch、name、email为必填字段,每个字段单独一行):
- 在本 Issue 下按如下格式评论(
/create_pr
branch: OLK-6.6 OLK-5.10
name: dev
email: dev@devstation.com
backport-engine: opencode
- 说明:
branch: 需要创建 PR 的目标分支列表,例如OLK-6.6 OLK-5.10;name: PR 签名人姓名(如责任人或安全负责人);email: PR 签名人邮箱;backport-engine(可选):可选portgpt、mystique或opencode;不填时默认使用opencode;
系统会根据上述信息自动在指定分支上创建 PR,并在本 Issue 下反馈结果。
provided by DevStation.


issue处理注意事项:
1. 提交正常修复分支的修复PR时,必须关联当前issue,否则无法关闭当前issue;
2. 模板内容需要填写完整, 无论是受影响或者不受影响都需要填写完整内容;
3. 以下为模板中需要填写完整的内容, 请复制到评论区回复;
注: 内容的关键词(影响性分析说明, openEuler评分, 受影响版本排查(受影响/不受影响), 修复是否涉及abi变化(是/否), 原因说明)不能省略,省略后cve-manager将无法正常解析填写内容.
影响性分析说明:
openEuler评分: (评分和向量)
受影响版本排查(受影响/不受影响):
1.master(6.18.40):
2.openEuler-20.03-LTS-SP4(4.19.90):
3.openEuler-22.03-LTS-SP4(5.10.0):
4.openEuler-24.03-LTS-Next(6.6.0):
5.openEuler-24.03-LTS-SP1(6.6.0):
6.openEuler-24.03-LTS-SP3(6.6.0):
7.openEuler-24.03-LTS-SP4(6.6.0):
修复是否涉及abi变化(是/否):
1.master(6.18.40):
2.openEuler-20.03-LTS-SP4(4.19.90):
3.openEuler-22.03-LTS-SP4(5.10.0):
4.openEuler-24.03-LTS-Next(6.6.0):
5.openEuler-24.03-LTS-SP1(6.6.0):
6.openEuler-24.03-LTS-SP3(6.6.0):
7.openEuler-24.03-LTS-SP4(6.6.0):
原因说明:
1.master(6.18.40):
2.openEuler-20.03-LTS-SP4(4.19.90):
3.openEuler-22.03-LTS-SP4(5.10.0):
4.openEuler-24.03-LTS-Next(6.6.0):
5.openEuler-24.03-LTS-SP1(6.6.0):
6.openEuler-24.03-LTS-SP3(6.6.0):
7.openEuler-24.03-LTS-SP4(6.6.0):
原因说明填写请参考下方表格(注意:版本是否受影响和版本的原因说明必须对应,例如master版本分支受影响,那原因说明只能是受影响对应的原因之一!):
分支状态 |
原因说明 | 使用场景 |
|---|---|---|
| 受影响 | 正常修复 | 受影响且需要修复(包含升级版本修复)的漏洞; 受影响且已经修复的漏洞(历史修复PR也需要关联issue); 若因特殊原因无法修复,应修改原因说明为【不修复-特殊原因】,并在安委会备案相关情况。 |
| 受影响 | 暂不修复-漏洞仍在分析中 | 已关注到相关漏洞,正在处理,未明确漏洞影响和修复方案。 |
| 受影响 | 暂不修复-暂无解决方案或补丁 | 当前没有可用的修复或补救措施。【影响性分析】中应包含有关为什么没有修复或补救措施的详细说明、上游相关PR等。 |
| 受影响 | 不修复-超出修复范围 | 没有漏洞的修复计划。当版本停维、软件包宣布生命周期终止或弃用使用。 |
| 受影响 | 不修复-特殊原因导致不再修复 | 如存在其他特殊情况不修复相关漏洞,或评估后无法升级修复,应在openEuler社区安全委员会例会进行说明备案。 【影响性分析】中应包含不发布修复的详细说明、特殊情况还应有安委会会议纪要。 |
| 受影响 | 应源码修复-openEuler社区发布软件包不受影响 | 源码存在漏洞,但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-99224 | None | None | https://git.kernel.org/stable/c/6b613747f7ea309ada5b8d05b55398c338f7a968 https://git.kernel.org/stable/c/0461bc8f91116aae4a020e15f4e1c1fd535ab35e https://git.kernel.org/stable/c/3c3cfd9e262afc9558c38f8cec57f09d10988546 https://git.kernel.org/stable/c/19c4de819e52b7f606468fbfe4fcef4e812e2777 https://git.kernel.org/stable/c/916667df7695366f23cfaf365b5840b228cc4b2e https://git.kernel.org/stable/c/a49e6c9a1a5b3457c946a8efb616ce13b4ca8194 https://git.kernel.org/stable/c/dea367df18e3a4faac393e3a4e818ee03af89b19 https://git.kernel.org/stable/c/dddd3a1ab7d12ee163477918ff6eb943361db4fe |
| https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2026-99224 | |||
| https://security-tracker.debian.org/tracker/CVE-2026-99224 | |||
| http://www.cnnvd.org.cn/web/vulnerability/queryLds.tag?qcvCnnvdid=CVE-2026-99224 | |||
| https://nvd.nist.gov/vuln/detail/CVE-2026-99224 | |||
| https://ubuntu.com/security/CVE-2026-99224 | 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


经过cve-manager解析,部分分支PR未合入,如红色字体所示:
原因说明:
1.master:不受影响-漏洞代码不能被攻击者触发
2.openEuler-20.03-LTS-SP4:暂不修复-漏洞仍在分析中
3.openEuler-22.03-LTS-SP3:不修复-超出修复范围
4.openEuler-22.03-LTS-SP4:正常修复
5.openEuler-24.03-LTS:不修复-超出修复范围
6.openEuler-24.03-LTS-Next:不受影响-漏洞代码不能被攻击者触发
7.openEuler-24.03-LTS-SP1:正常修复(PR未合入)
8.openEuler-24.03-LTS-SP2:不修复-超出修复范围
9.openEuler-24.03-LTS-SP3:正常修复(PR未合入)
10.openEuler-24.03-LTS-SP4:正常修复(PR未合入)


一、漏洞信息
漏洞编号:CVE-2026-99224
漏洞归属组件:kernel
漏洞归属的版本:4.19.140,4.19.90,5.10.0,6.1.19,6.18.40,6.18.56,6.4.0,6.6.0
CVSS评分:
BaseScore:7.0 High
Vector:CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
漏洞简述:
In the Linux kernel, the following vulnerability has been resolved:keys: Protect the type name while describing a keykeyctl_describe_key() must keep the key type s name alive untilkasprintf() has consumed it. The retained key reference keeps the keyand its description alive, but does not pin the module providing itstype. The name is passed to kasprintf() without holding key->sem.kvasprintf() uses the saved name pointer in two formatting passes, witha GFP_KERNEL allocation between them. With AF_RXRPC=m, a task thatpasses View permission before type retirement can overlap a privilegedmodule unload in this order:1. KEYCTL_DESCRIBE looks up the key, saves key->type->name in the kasprintf() arguments and completes the first formatting pass.2. While the formatter is delayed before its second pass, af_rxrpc_exit() calls unregister_key_type(), which removes the type from the registry and waits for key_gc_keytype().3. The collector takes key->sem for writing, retypes the retained key to key_type_dead and completes retirement. Unregistration and module exit return, allowing free_module() to release the type and name.4. The formatter resumes its second pass and reads the saved name from released module storage, which can fault in string().Hold key->sem for reading across kasprintf(). The collector then cannotretype the key or complete retirement until both formatting passes havefinished. If retirement wins the lock first, formatting uses the corekey_type_dead name instead. Release the semaphore immediately afterkasprintf(), including on allocation failure, before copying touserspace.Oops report as below: BUG: unable to handle page fault for address: fffffbfff8054794 #PF: supervisor read access in kernel mode #PF: error_code(0x0000) - not-present page RIP: 0010:string+0x23f/0x470 Call Trace: vsnprintf+0x330/0x1110
漏洞公开时间:2026-11-03 00:17:46
漏洞创建时间:2026-11-03 01:15:09
漏洞详情参考链接:
https://nvd.nist.gov/vuln/detail/CVE-2026-99224
更多参考(点击展开)
漏洞分析指导链接:
https://atomgit.com/openeuler/cve-manager/blob/master/cve-vulner-manager/doc/md/manual.md
漏洞数据来源:
七彩瞬析开源风险感知平台
漏洞补丁信息:
详情(点击展开)
二、漏洞分析结构反馈
影响性分析说明:
In the Linux kernel, the following vulnerability has been resolved:keys: Protect the type name while describing a keykeyctl_describe_key() must keep the key type s name alive untilkasprintf() has consumed it. The retained key reference keeps the keyand its description alive, but does not pin the module providing itstype. The name is passed to kasprintf() without holding key->sem.kvasprintf() uses the saved name pointer in two formatting passes, witha GFP_KERNEL allocation between them. With AF_RXRPC=m, a task thatpasses View permission before type retirement can overlap a privilegedmodule unload in this order:1. KEYCTL_DESCRIBE looks up the key, saves key->type->name in the kasprintf() arguments and completes the first formatting pass.2. While the formatter is delayed before its second pass, af_rxrpc_exit() calls unregister_key_type(), which removes the type from the registry and waits for key_gc_keytype().3. The collector takes key->sem for writing, retypes the retained key to key_type_dead and completes retirement. Unregistration and module exit return, allowing free_module() to release the type and name.4. The formatter resumes its second pass and reads the saved name from released module storage, which can fault in string().Hold key->sem for reading across kasprintf(). The collector then cannotretype the key or complete retirement until both formatting passes havefinished. If retirement wins the lock first, formatting uses the corekey_type_dead name instead. Release the semaphore immediately afterkasprintf(), including on allocation failure, before copying touserspace.Oops report as below: BUG: unable to handle page fault for address: fffffbfff8054794 #PF: supervisor read access in kernel mode #PF: error_code(0x0000) - not-present page RIP: 0010:string+0x23f/0x470 Call Trace: vsnprintf+0x330/0x1110
openEuler评分:
7.0
Vector:CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
受影响版本排查(受影响/不受影响):
1.master(7.3.0):不受影响
2.openEuler-20.03-LTS-SP4(4.19.90):受影响
3.openEuler-22.03-LTS-SP3(5.10.0):受影响
4.openEuler-22.03-LTS-SP4(5.10.0):受影响
5.openEuler-24.03-LTS(6.6.0):受影响
6.openEuler-24.03-LTS-Next(6.6.0):不受影响
7.openEuler-24.03-LTS-SP1(6.6.0):受影响
8.openEuler-24.03-LTS-SP2(6.6.0):受影响
9.openEuler-24.03-LTS-SP3(6.6.0):受影响
10.openEuler-24.03-LTS-SP4(6.6.0):受影响
修复是否涉及abi变化(是/否):
1.master(7.3.0):否
2.openEuler-20.03-LTS-SP4(4.19.90):否
3.openEuler-22.03-LTS-SP3(5.10.0):否
4.openEuler-22.03-LTS-SP4(5.10.0):否
5.openEuler-24.03-LTS(6.6.0):否
6.openEuler-24.03-LTS-Next(6.6.0):否
7.openEuler-24.03-LTS-SP1(6.6.0):否
8.openEuler-24.03-LTS-SP2(6.6.0):否
9.openEuler-24.03-LTS-SP3(6.6.0):否
10.openEuler-24.03-LTS-SP4(6.6.0):否
原因说明:
1.master(7.3.0):不受影响-漏洞代码不能被攻击者触发
2.openEuler-20.03-LTS-SP4(4.19.90):暂不修复-漏洞仍在分析中
3.openEuler-22.03-LTS-SP3(5.10.0):不修复-超出修复范围
4.openEuler-22.03-LTS-SP4(5.10.0):正常修复
5.openEuler-24.03-LTS(6.6.0):不修复-超出修复范围
6.openEuler-24.03-LTS-Next(6.6.0):不受影响-漏洞代码不能被攻击者触发
7.openEuler-24.03-LTS-SP1(6.6.0):正常修复
8.openEuler-24.03-LTS-SP2(6.6.0):不修复-超出修复范围
9.openEuler-24.03-LTS-SP3(6.6.0):正常修复
10.openEuler-24.03-LTS-SP4(6.6.0):正常修复