检测到新建 CVE Issue,CVE-ID: CVE-2026-90174。
你可以通过以下两种方式使用 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社区安全委员会例会进行说明备案。 【影响性分析】中应包含不发布修复的详细说明、特殊情况还应有安委会会议纪要。 |
| 不受影响 | 不受影响-组件不存在 | 软件不受影响,因为易受攻击的组件不在产品中。 |
| 不受影响 | 不受影响-已有内置的内联控制或缓解措施 | 内置的内联控制或缓解措施可防止攻击者利用漏洞 |
| 不受影响 | 不受影响-漏洞代码不能被攻击者触发 | 易受攻击的组件存在,并且该组件包含易受攻击的代码。但是,易受攻击的代码的使用方式使得攻击者无法进行任何预期的攻击。 |
| 不受影响 | 不受影响-漏洞代码不在执行路径 | 易受影响的代码在执行过程中不可访问,包括产品的非预期状态。产品不使用也不执行的组件。 |
| 不受影响 | 不受影响-漏洞代码不存在 | 产品不受影响,因为漏洞背后的代码在产品中不存在。与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-90174 | None | None | https://git.kernel.org/stable/c/497c221bf6b2f659511719a6acfae84cc1be1caf https://git.kernel.org/stable/c/7405d0ba294306721843bc551611775e6edef516 |
| https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2026-90174 | |||
| https://security-tracker.debian.org/tracker/CVE-2026-90174 | None | None | https://git.kernel.org/linus/7405d0ba294306721843bc551611775e6edef516 |
| http://www.cnnvd.org.cn/web/vulnerability/queryLds.tag?qcvCnnvdid=CVE-2026-90174 | |||
| https://nvd.nist.gov/vuln/detail/CVE-2026-90174 | |||
| https://ubuntu.com/security/CVE-2026-90174 | 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


@zhangxiaoxv CVE信息从NVD同步失败, 请稍后重试, 或者数据源不存在.


Welcome To openEuler Community
Hey @zhangxiaoxv , 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: Kernel ,
and any of the maintainers: @hanjunguo, @oekernel, @sanglipeng, @wkfxxx, @zeng_zhaorong ,
and any of the committers: @CTC-XiboWang, @Frank_Sae, @GoGo_phytium, @GongLei-, @LiuYongQiang0816, @SuperSix173, @Tankll2021, @TrueAI, @YiweiZ, @allen-shi, @alvin-ling, @baratta, @bibo_mao, @caixu-blue, @chen-jun-hw, @chenjiesong, @chenjunxin1992, @chenke2026, @chiqijun, @chriszjh, @duanqiangwen, @eingesch, @fangfeng123, @fanghaiqinghw, @gang_he, @gaojuxin09, @gouhao2022, @guohaocs2c, @guzitao, @hanjunguo, @hanliyang, @hellotcc, @henryze, @hewanhan, @hjx_gitff, @hongwu-wang, @howard_lu, @htforge, @hu-chunzhi, @hunan4222, @jackknight, @jerry_lilijun, @jiayi0118, @junlong-zheng, @juntianlinux, @kailiu42, @kaitiandu, @kazero00, @kevinzhu1, @kile2009, @klmengkd, @koishimind, @kongzizaixian, @kunlun_spurs, @kylin-mayukun, @leoliu-oc, @li-huisong, @linan888, @linyunsheng, @liulongfang, @liyihang0226, @lostway1, @lujialin2, @mao-hongbo, @markyuan4ta21, @mawupeng, @mingqian218472, @mingrui-liu, @mufengyan, @nebulamatrix_rdma, @peterpangogogo, @pigalsofine, @robinorg, @rock_hw, @sanglipeng, @shu-shengming, @shuaijiakun, @siyanteng, @sming56_admin, @stavewu, @stkid, @sun_nanyong, @wangboe2022, @wanghang73, @wenzhiwei11, @whoisxxx, @wkfxxx, @woqidaideshi, @wsoydl, @xingmz1, @xukuohai, @yeweihua999, @ygn-ndwd-official, @yonghu_4dc5, @young-sun, @yubo-liu1, @yuehaibing_planb, @yuzenghui1, @zhang-changzhong, @zhangyi089, @zhujianwei001, @zichengqu, @zouyipeng, @zqiao216 .


CVE-2026-90174
影响性分析说明:
In the Linux kernel, the following vulnerability has been resolved:
ksmbd: fix slab-out-of-bounds read in ksmbd_alloc_user()
ksmbd_alloc_user() copies resp->hash_sz bytes out of the mountd IPC
login response with
user->passkey_sz = resp->hash_sz;
user->passkey = kmalloc(resp->hash_sz, KSMBD_DEFAULT_GFP);
if (user->passkey)
memcpy(user->passkey, resp->hash, resp->hash_sz);
resp->hash_sz is a __u16 supplied by the response, but resp->hash[] is
only KSMBD_REQ_MAX_HASH_SZ bytes. A malformed or malicious login
response can set hash_sz well beyond that (up to 65535), so the memcpy()
reads past the end of the response object. ipc_validate_msg() does not
bound hash_sz, so reject any response whose hash_sz exceeds the on-stack
hash[] buffer before allocating and copying.
[ 2030.238706] BUG: KASAN: slab-out-of-bounds in ksmbd_alloc_user+0x278/0x680
[ 2030.240549] Read of size 65535 at addr ffff888121bb6680 by task kworker/4:1/18611
[ 2030.242296]
[ 2030.242710] CPU: 4 UID: 0 PID: 18611 Comm: kworker/4:1 Not tainted 7.1.0-next-20260623-virtme #96 PREEMPT(lazy)
[ 2030.242732] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.17.0-debian-1.17.0-1 04/01/2014
[ 2030.242743] Workqueue: ksmbd-io handle_ksmbd_work
[ 2030.242763] Call Trace:
[ 2030.242769]
[ 2030.242776] dump_stack_lvl+0xa2/0xd0
[ 2030.242794] print_address_description+0x77/0x200
[ 2030.242815] ? ksmbd_alloc_user+0x278/0x680
[ 2030.242831] print_report+0x58/0x70
[ 2030.242848] kasan_report+0x117/0x150
[ 2030.242869] ? ksmbd_alloc_user+0x278/0x680
[ 2030.242888] kasan_check_range+0x3c7/0x3f0
[ 2030.242908] ? ksmbd_alloc_user+0x278/0x680
[ 2030.242925] __asan_memcpy+0x29/0x70
[ 2030.242942] ksmbd_alloc_user+0x278/0x680
[ 2030.242960] ksmbd_login_user+0xc3/0x120
[ 2030.242978] ntlm_authenticate+0x5e6/0x1b00
[ 2030.243017] ? __pfx_ntlm_authenticate+0x10/0x10
[ 2030.243035] ? ksmbd_session_lookup+0x188/0x1d0
[ 2030.243054] ? __pfx_ksmbd_session_lookup+0x10/0x10
[ 2030.243090] ? __sanitizer_cov_trace_switch+0x7b/0x140
[ 2030.243108] smb2_sess_setup+0x1e4a/0x27b0
[ 2030.243126] ? copy_from_kernel_nofault+0x199/0x300
[ 2030.243156] ? __pfx_smb2_sess_setup+0x10/0x10
[ 2030.243173] ? get_smb2_cmd_val+0xe3/0x1c0
[ 2030.243208] handle_ksmbd_work+0x954/0x1280
[ 2030.243230] ? __pfx_handle_ksmbd_work+0x10/0x10
[ 2030.243249] ? process_scheduled_works+0xa07/0x1490
[ 2030.243270] ? process_scheduled_works+0xa07/0x1490
[ 2030.243291] process_scheduled_works+0xa70/0x1490
[ 2030.243320] ? __pfx_process_scheduled_works+0x10/0x10
[ 2030.243340] ? do_raw_spin_lock+0x130/0x300
[ 2030.243358] ? lock_is_held_type+0x7b/0x110
[ 2030.243388] worker_thread+0x932/0xe20
[ 2030.243415] kthread+0x38a/0x470
[ 2030.243431] ? __pfx_worker_thread+0x10/0x10
[ 2030.243451] ? __pfx_kthread+0x10/0x10
[ 2030.243467] ret_from_fork+0x484/0x910
[ 2030.243485] ? __pfx_ret_from_fork+0x10/0x10
[ 2030.243501] ? __switch_to+0xc77/0x12c0
[ 2030.243523] ? __pfx_kthread+0x10/0x10
[ 2030.243540] ret_from_fork_asm+0x1a/0x30
[ 2030.243564]
[ 2030.243570]
[ 2030.290164] Allocated by task 19279:
[ 2030.290911] kasan_save_track+0x3e/0x80
[ 2030.292179] __kasan_kmalloc+0x72/0x90
[ 2030.293217] __kvmalloc_node_noprof+0x3ff/0x6b0
[ 2030.294467] handle_generic_event+0x59b/0x750
[ 2030.295345] genl_family_rcv_msg_doit+0x238/0x340
[ 2030.296553] genl_rcv_msg+0x606/0x7b0
[ 2030.297129] netlink_rcv_skb+0x22b/0x4a0
[ 2030.298500] genl_rcv+0x2d/0x40
[ 2030.299273] netlink_unicast+0x7ba/0x930
[ 2030.300019] netlink_sendmsg+0x8c3/0xb00
[ 2030.301073] __sock_sendmsg+0xec/0x140
[ 2030.301579] __sys_sendto+0x357/0x470
[ 2030.302255] __x64_sys_sendto+0xe3/0x100
[ 2030.303425] do_syscall_64+0x135/0x460
[ 2030.304763] entry_SYSCALL_64_after_hwframe+0x77/0x7f
[ 2030.305594]
[ 2030.305819] The buggy address belongs to the object at ffff888121bb6640
[ 2030.305819] which belongs to the cache kmalloc-192 of size 192
[ 2030.309595] The buggy address
---truncated---
openEuler评分:(评分和向量)
7.1
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
受影响版本排查(受影响/不受影响):
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:受影响
8.openEuler-24.03-LTS-SP2:受影响
9.openEuler-24.03-LTS-SP3:受影响
10.openEuler-24.03-LTS-SP4:受影响
修复是否涉及abi变化(是/否):
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:否
8.openEuler-24.03-LTS-SP2:否
9.openEuler-24.03-LTS-SP3:否
10.openEuler-24.03-LTS-SP4:否
原因说明:
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:暂不修复-漏洞仍在分析中
8.openEuler-24.03-LTS-SP2:不修复-超出修复范围
9.openEuler-24.03-LTS-SP3:暂不修复-漏洞仍在分析中
10.openEuler-24.03-LTS-SP4:暂不修复-漏洞仍在分析中


@wkfxxx 经过 cve-manager 解析, 已分析的内容如下表所示:
| 状态 | 分析项目 | 内容 |
|---|---|---|
| 已分析 | 1.影响性分析说明 | In the Linux kernel, the following vulnerability has been resolved:ksmbd: fix slab-out-of-bounds read in ksmbd_alloc_user()ksmbd_alloc_user() copies resp->hash_sz bytes out of the mountd IPClogin response withuser->passkey_sz = resp->hash_sz;user->passkey = kmalloc(resp->hash_sz, KSMBD_DEFAULT_GFP);if (user->passkey)memcpy(user->passkey, resp->hash, resp->hash_sz);resp->hash_sz is a __u16 supplied by the response, but resp->hash[] isonly KSMBD_REQ_MAX_HASH_SZ bytes. A malformed or malicious loginresponse can set hash_sz well beyond that (up to 65535), so the memcpy()reads past the end of the response object. ipc_validate_msg() does notbound hash_sz, so reject any response whose hash_sz exceeds the on-stackhash[] buffer before allocating and copying.[ 2030.238706] BUG: KASAN: slab-out-of-bounds in ksmbd_alloc_user+0x278/0x680[ 2030.240549] Read of size 65535 at addr ffff888121bb6680 by task kworker/4:1/18611[ 2030.242296][ 2030.242710] CPU: 4 UID: 0 PID: 18611 Comm: kworker/4:1 Not tainted 7.1.0-next-20260623-virtme #96 PREEMPT(lazy)[ 2030.242732] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.17.0-debian-1.17.0-1 04/01/2014[ 2030.242743] Workqueue: ksmbd-io handle_ksmbd_work[ 2030.242763] Call Trace:[ 2030.242769] |
| 已分析 | 2.openEulerScore | 7.1 |
| 已分析 | 3.openEulerVector | AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H |
| 已分析 | 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:受影响,openEuler-22.03-LTS-SP3:受影响,openEuler-24.03-LTS:受影响,openEuler-24.03-LTS-SP2:受影响 |
| 已分析 | 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:否,openEuler-22.03-LTS-SP3:否,openEuler-24.03-LTS:否,openEuler-24.03-LTS-SP2:否 |
| 已分析 | 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:暂不修复-漏洞仍在分析中,openEuler-22.03-LTS-SP3:不修复-超出修复范围,openEuler-24.03-LTS:不修复-超出修复范围,openEuler-24.03-LTS-SP2:不修复-超出修复范围 |
请确认分析内容的准确性, 确认无误后, 您可以进行后续步骤, 否则您可以继续分析.


一、漏洞信息[ 2030.242776] dump_stack_lvl+0xa2/0xd0[ 2030.242794] print_address_description+0x77/0x200[ 2030.242815] ? ksmbd_alloc_user+0x278/0x680[ 2030.242831] print_report+0x58/0x70[ 2030.242848] kasan_report+0x117/0x150[ 2030.242869] ? ksmbd_alloc_user+0x278/0x680[ 2030.242888] kasan_check_range+0x3c7/0x3f0[ 2030.242908] ? ksmbd_alloc_user+0x278/0x680[ 2030.242925] __asan_memcpy+0x29/0x70[ 2030.242942] ksmbd_alloc_user+0x278/0x680[ 2030.242960] ksmbd_login_user+0xc3/0x120[ 2030.242978] ntlm_authenticate+0x5e6/0x1b00[ 2030.243017] ? __pfx_ntlm_authenticate+0x10/0x10[ 2030.243035] ? ksmbd_session_lookup+0x188/0x1d0[ 2030.243054] ? __pfx_ksmbd_session_lookup+0x10/0x10[ 2030.243090] ? __sanitizer_cov_trace_switch+0x7b/0x140[ 2030.243108] smb2_sess_setup+0x1e4a/0x27b0[ 2030.243126] ? copy_from_kernel_nofault+0x199/0x300[ 2030.243156] ? __pfx_smb2_sess_setup+0x10/0x10[ 2030.243173] ? get_smb2_cmd_val+0xe3/0x1c0[ 2030.243208] handle_ksmbd_work+0x954/0x1280[ 2030.243230] ? __pfx_handle_ksmbd_work+0x10/0x10[ 2030.243249] ? process_scheduled_works+0xa07/0x1490[ 2030.243270] ? process_scheduled_works+0xa07/0x1490[ 2030.243291] process_scheduled_works+0xa70/0x1490[ 2030.243320] ? __pfx_process_scheduled_works+0x10/0x10[ 2030.243340] ? do_raw_spin_lock+0x130/0x300[ 2030.243358] ? lock_is_held_type+0x7b/0x110[ 2030.243388] worker_thread+0x932/0xe20[ 2030.243415] kthread+0x38a/0x470[ 2030.243431] ? __pfx_worker_thread+0x10/0x10[ 2030.243451] ? __pfx_kthread+0x10/0x10[ 2030.243467] ret_from_fork+0x484/0x910[ 2030.243485] ? __pfx_ret_from_fork+0x10/0x10[ 2030.243501] ? __switch_to+0xc77/0x12c0[ 2030.243523] ? __pfx_kthread+0x10/0x10[ 2030.243540] ret_from_fork_asm+0x1a/0x30[ 2030.243564] [ 2030.243570][ 2030.290164] Allocated by task 19279:[ 2030.290911] kasan_save_track+0x3e/0x80[ 2030.292179] __kasan_kmalloc+0x72/0x90[ 2030.293217] __kvmalloc_node_noprof+0x3ff/0x6b0[ 2030.294467] handle_generic_event+0x59b/0x750[ 2030.295345] genl_family_rcv_msg_doit+0x238/0x340[ 2030.296553] genl_rcv_msg+0x606/0x7b0[ 2030.297129] netlink_rcv_skb+0x22b/0x4a0[ 2030.298500] genl_rcv+0x2d/0x40[ 2030.299273] netlink_unicast+0x7ba/0x930[ 2030.300019] netlink_sendmsg+0x8c3/0xb00[ 2030.301073] __sock_sendmsg+0xec/0x140[ 2030.301579] __sys_sendto+0x357/0x470[ 2030.302255] __x64_sys_sendto+0xe3/0x100[ 2030.303425] do_syscall_64+0x135/0x460[ 2030.304763] entry_SYSCALL_64_after_hwframe+0x77/0x7f[ 2030.305594][ 2030.305819] The buggy address belongs to the object at ffff888121bb6640[ 2030.305819] which belongs to the cache kmalloc-192 of size 192[ 2030.309595] The buggy address ---truncated---
漏洞编号:CVE-2026-90174
漏洞归属组件:kernel
漏洞归属的版本:5.10.0
CVSS评分:
BaseScore:7.1 High
Vector:CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
漏洞简述:
In the Linux kernel, the following vulnerability has been resolved:ksmbd: fix slab-out-of-bounds read in ksmbd_alloc_user()ksmbd_alloc_user() copies resp->hash_sz bytes out of the mountd IPClogin response with user->passkey_sz = resp->hash_sz; user->passkey = kmalloc(resp->hash_sz, KSMBD_DEFAULT_GFP); if (user->passkey) memcpy(user->passkey, resp->hash, resp->hash_sz);resp->hash_sz is a __u16 supplied by the response, but resp->hash[] isonly KSMBD_REQ_MAX_HASH_SZ bytes. A malformed or malicious loginresponse can set hash_sz well beyond that (up to 65535), so the memcpy()reads past the end of the response object. ipc_validate_msg() does notbound hash_sz, so reject any response whose hash_sz exceeds the on-stackhash[] buffer before allocating and copying.[ 2030.238706] BUG: KASAN: slab-out-of-bounds in ksmbd_alloc_user+0x278/0x680[ 2030.240549] Read of size 65535 at addr ffff888121bb6680 by task kworker/4:1/18611[ 2030.242296][ 2030.242710] CPU: 4 UID: 0 PID: 18611 Comm: kworker/4:1 Not tainted 7.1.0-next-20260623-virtme #96 PREEMPT(lazy)[ 2030.242732] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.17.0-debian-1.17.0-1 04/01/2014[ 2030.242743] Workqueue: ksmbd-io handle_ksmbd_work[ 2030.242763] Call Trace:[ 2030.242769]
漏洞公开时间:2026-09-18 01:17:11
漏洞创建时间:2026-09-21 02:31:46
漏洞详情参考链接:
https://nvd.nist.gov/vuln/detail/CVE-2026-90174
更多参考(点击展开)
无
漏洞分析指导链接:
https://atomgit.com/openeuler/cve-manager/blob/master/cve-vulner-manager/doc/md/manual.md
漏洞数据来源:
其他
漏洞补丁信息:
详情(点击展开)
无
二、漏洞分析结构反馈[ 2030.242776] dump_stack_lvl+0xa2/0xd0[ 2030.242794] print_address_description+0x77/0x200[ 2030.242815] ? ksmbd_alloc_user+0x278/0x680[ 2030.242831] print_report+0x58/0x70[ 2030.242848] kasan_report+0x117/0x150[ 2030.242869] ? ksmbd_alloc_user+0x278/0x680[ 2030.242888] kasan_check_range+0x3c7/0x3f0[ 2030.242908] ? ksmbd_alloc_user+0x278/0x680[ 2030.242925] __asan_memcpy+0x29/0x70[ 2030.242942] ksmbd_alloc_user+0x278/0x680[ 2030.242960] ksmbd_login_user+0xc3/0x120[ 2030.242978] ntlm_authenticate+0x5e6/0x1b00[ 2030.243017] ? __pfx_ntlm_authenticate+0x10/0x10[ 2030.243035] ? ksmbd_session_lookup+0x188/0x1d0[ 2030.243054] ? __pfx_ksmbd_session_lookup+0x10/0x10[ 2030.243090] ? __sanitizer_cov_trace_switch+0x7b/0x140[ 2030.243108] smb2_sess_setup+0x1e4a/0x27b0[ 2030.243126] ? copy_from_kernel_nofault+0x199/0x300[ 2030.243156] ? __pfx_smb2_sess_setup+0x10/0x10[ 2030.243173] ? get_smb2_cmd_val+0xe3/0x1c0[ 2030.243208] handle_ksmbd_work+0x954/0x1280[ 2030.243230] ? __pfx_handle_ksmbd_work+0x10/0x10[ 2030.243249] ? process_scheduled_works+0xa07/0x1490[ 2030.243270] ? process_scheduled_works+0xa07/0x1490[ 2030.243291] process_scheduled_works+0xa70/0x1490[ 2030.243320] ? __pfx_process_scheduled_works+0x10/0x10[ 2030.243340] ? do_raw_spin_lock+0x130/0x300[ 2030.243358] ? lock_is_held_type+0x7b/0x110[ 2030.243388] worker_thread+0x932/0xe20[ 2030.243415] kthread+0x38a/0x470[ 2030.243431] ? __pfx_worker_thread+0x10/0x10[ 2030.243451] ? __pfx_kthread+0x10/0x10[ 2030.243467] ret_from_fork+0x484/0x910[ 2030.243485] ? __pfx_ret_from_fork+0x10/0x10[ 2030.243501] ? __switch_to+0xc77/0x12c0[ 2030.243523] ? __pfx_kthread+0x10/0x10[ 2030.243540] ret_from_fork_asm+0x1a/0x30[ 2030.243564] [ 2030.243570][ 2030.290164] Allocated by task 19279:[ 2030.290911] kasan_save_track+0x3e/0x80[ 2030.292179] __kasan_kmalloc+0x72/0x90[ 2030.293217] __kvmalloc_node_noprof+0x3ff/0x6b0[ 2030.294467] handle_generic_event+0x59b/0x750[ 2030.295345] genl_family_rcv_msg_doit+0x238/0x340[ 2030.296553] genl_rcv_msg+0x606/0x7b0[ 2030.297129] netlink_rcv_skb+0x22b/0x4a0[ 2030.298500] genl_rcv+0x2d/0x40[ 2030.299273] netlink_unicast+0x7ba/0x930[ 2030.300019] netlink_sendmsg+0x8c3/0xb00[ 2030.301073] __sock_sendmsg+0xec/0x140[ 2030.301579] __sys_sendto+0x357/0x470[ 2030.302255] __x64_sys_sendto+0xe3/0x100[ 2030.303425] do_syscall_64+0x135/0x460[ 2030.304763] entry_SYSCALL_64_after_hwframe+0x77/0x7f[ 2030.305594][ 2030.305819] The buggy address belongs to the object at ffff888121bb6640[ 2030.305819] which belongs to the cache kmalloc-192 of size 192[ 2030.309595] The buggy address ---truncated---
影响性分析说明:
In the Linux kernel, the following vulnerability has been resolved:ksmbd: fix slab-out-of-bounds read in ksmbd_alloc_user()ksmbd_alloc_user() copies resp->hash_sz bytes out of the mountd IPClogin response withuser->passkey_sz = resp->hash_sz;user->passkey = kmalloc(resp->hash_sz, KSMBD_DEFAULT_GFP);if (user->passkey)memcpy(user->passkey, resp->hash, resp->hash_sz);resp->hash_sz is a __u16 supplied by the response, but resp->hash[] isonly KSMBD_REQ_MAX_HASH_SZ bytes. A malformed or malicious loginresponse can set hash_sz well beyond that (up to 65535), so the memcpy()reads past the end of the response object. ipc_validate_msg() does notbound hash_sz, so reject any response whose hash_sz exceeds the on-stackhash[] buffer before allocating and copying.[ 2030.238706] BUG: KASAN: slab-out-of-bounds in ksmbd_alloc_user+0x278/0x680[ 2030.240549] Read of size 65535 at addr ffff888121bb6680 by task kworker/4:1/18611[ 2030.242296][ 2030.242710] CPU: 4 UID: 0 PID: 18611 Comm: kworker/4:1 Not tainted 7.1.0-next-20260623-virtme #96 PREEMPT(lazy)[ 2030.242732] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.17.0-debian-1.17.0-1 04/01/2014[ 2030.242743] Workqueue: ksmbd-io handle_ksmbd_work[ 2030.242763] Call Trace:[ 2030.242769]
openEuler评分:
7.1
Vector:CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
受影响版本排查(受影响/不受影响):
1.master(7.3.0):不受影响
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):受影响
8.openEuler-22.03-LTS-SP3(5.10.0):受影响
9.openEuler-24.03-LTS(6.6.0):受影响
10.openEuler-24.03-LTS-SP2(6.6.0):受影响
修复是否涉及abi变化(是/否):
1.master(7.3.0):否
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):否
8.openEuler-22.03-LTS-SP3(5.10.0):否
9.openEuler-24.03-LTS(6.6.0):否
10.openEuler-24.03-LTS-SP2(6.6.0):否
原因说明:
1.master(7.3.0):不受影响-漏洞代码不能被攻击者触发
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):暂不修复-漏洞仍在分析中
8.openEuler-22.03-LTS-SP3(5.10.0):不修复-超出修复范围
9.openEuler-24.03-LTS(6.6.0):不修复-超出修复范围
10.openEuler-24.03-LTS-SP2(6.6.0):不修复-超出修复范围