已开启
CVE-2026-98362 #20040
openeuler-ci-bot创建于  26 天前
openeuler-ci-bot
openeuler-ci-bot成员
26 天前 创建

一、漏洞信息
漏洞编号:CVE-2026-98362
漏洞归属组件:kernel
漏洞归属的版本:4.19.140,4.19.90,5.10.0,6.1.19,6.18.40,6.18.48,6.4.0,6.6.0
CVSS评分:
BaseScore:0.0 None
Vector:
漏洞简述:
In the Linux kernel, the following vulnerability has been resolved:clk: scpi: bound-check DVFS index in scpi_dvfs_recalc_ratedvfs_get_idx() may return an out-of-range index if the SCP firmware isbuggy or returns a stale value. Only negative indexes were rejected, so alarge index walked past info->opps and could treat garbage as a clock rate(KASAN OOB / wrong frequency to consumers). The missing upper bound datesback to the original SCPI clock driver.Treat indexes >= opp count as invalid and return 0, same as idx < 0.
漏洞公开时间:2026-10-06 08:46:48
漏洞创建时间:2026-10-06 20:47:16
漏洞详情参考链接:
https://nvd.nist.gov/vuln/detail/CVE-2026-98362

更多参考(点击展开)
参考来源 参考链接 来源链接
https://www.first.org/epss
https://git.kernel.org/stable/c/6e3b55823da8ef0d99621efb422cc29f50d7f280
https://lore.kernel.org/linux-cve-announce/2026100621-CVE-2026-98362-ed1c@gregkh/T/#u
https://git.kernel.org/stable/c/0f89e2ac0e945da2ce798f6a61aebf9d291c2e0a
https://git.kernel.org/stable/c/70f4b78d560e592cbf3325b162424737d032fc1d
https://git.kernel.org/stable/c/e1188332a9110cf3635fe286481ee38305b3c2b6
https://git.kernel.org/stable/c/a82b274697d0876b478594ca78ad1e6cb062467b
https://git.kernel.org/stable/c/56b7a9d89c67932bf11b71e3b6d17941fc24a393
https://nvd.nist.gov/vuln/detail/CVE-2026-98362
https://git.kernel.org/stable/c/108c46e8dacc4a0e472a74f98171115d49cbc079
https://github.com/secwatch-io/bookingpro-poc
https://cwe.mitre.org/data/definitions/89.html
https://git.kernel.org/stable/c/7204095917aeaac89db7377c29a457351a19b076

漏洞分析指导链接:
https://atomgit.com/openeuler/cve-manager/blob/master/cve-vulner-manager/doc/md/manual.md
漏洞数据来源:
七彩瞬析开源风险感知平台
漏洞补丁信息:

详情(点击展开)
影响的包 修复版本 修复补丁 问题引入补丁 来源
gregkh/linux https://git.kernel.org/stable/c/0f89e2ac0e945da2ce798f6a61aebf9d291c2e0a ljqc
gregkh/linux https://git.kernel.org/stable/c/108c46e8dacc4a0e472a74f98171115d49cbc079 ljqc
gregkh/linux https://git.kernel.org/stable/c/56b7a9d89c67932bf11b71e3b6d17941fc24a393 ljqc
gregkh/linux https://git.kernel.org/stable/c/6e3b55823da8ef0d99621efb422cc29f50d7f280 ljqc
gregkh/linux https://git.kernel.org/stable/c/70f4b78d560e592cbf3325b162424737d032fc1d ljqc
gregkh/linux https://git.kernel.org/stable/c/7204095917aeaac89db7377c29a457351a19b076 ljqc
gregkh/linux https://git.kernel.org/stable/c/a82b274697d0876b478594ca78ad1e6cb062467b ljqc
gregkh/linux https://git.kernel.org/stable/c/e1188332a9110cf3635fe286481ee38305b3c2b6 ljqc
https://git.kernel.org/stable/c/6e3b55823da8ef0d99621efb422cc29f50d7f280 cybersecurity
https://git.kernel.org/stable/c/0f89e2ac0e945da2ce798f6a61aebf9d291c2e0a cybersecurity
https://git.kernel.org/stable/c/70f4b78d560e592cbf3325b162424737d032fc1d cybersecurity
https://git.kernel.org/stable/c/e1188332a9110cf3635fe286481ee38305b3c2b6 cybersecurity
https://git.kernel.org/stable/c/a82b274697d0876b478594ca78ad1e6cb062467b cybersecurity
https://git.kernel.org/stable/c/56b7a9d89c67932bf11b71e3b6d17941fc24a393 cybersecurity
https://git.kernel.org/stable/c/108c46e8dacc4a0e472a74f98171115d49cbc079 cybersecurity
https://git.kernel.org/stable/c/7204095917aeaac89db7377c29a457351a19b076 cybersecurity

二、漏洞分析结构反馈
影响性分析说明:
In the Linux kernel, the following vulnerability has been resolved:clk: scpi: bound-check DVFS index in scpi_dvfs_recalc_ratedvfs_get_idx() may return an out-of-range index if the SCP firmware isbuggy or returns a stale value. Only negative indexes were rejected, so alarge index walked past info->opps and could treat garbage as a clock rate(KASAN OOB / wrong frequency to consumers). The missing upper bound datesback to the original SCPI clock driver.Treat indexes >= opp count as invalid and return 0, same as idx < 0.The Linux kernel CVE team has assigned CVE-2026-98362 to this issue.
openEuler评分:
9.8
Vector:CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
受影响版本排查(受影响/不受影响):
1.master(6.18.40):不受影响
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(6.18.40):否
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(6.18.40):不受影响-漏洞代码不能被攻击者触发
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):正常修复

likedislike
openeuler-ci-botopeneuler-ci-bot成员
26 天前 添加了label:CVE/UNFIXED
openeuler-ci-bot
openeuler-ci-bot成员
26 天前 评论:

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

likedislike
openeuler-ci-botopeneuler-ci-bot成员
26 天前 将 wkfxxx、openeuler-ci-bot、zeng_zhaorong、sanglipeng、oekernel、hanjunguo 设为负责人
openeuler-ci-botopeneuler-ci-bot成员
26 天前 添加了label:sig/Kernel
openeuler-ci-bot
openeuler-ci-bot成员
26 天前 评论:
参考网址 关联pr 状态 补丁链接
https://www.opencve.io/cve/CVE-2026-98362NoneNonehttps://git.kernel.org/stable/c/7204095917aeaac89db7377c29a457351a19b076
https://git.kernel.org/stable/c/6e3b55823da8ef0d99621efb422cc29f50d7f280
https://git.kernel.org/stable/c/0f89e2ac0e945da2ce798f6a61aebf9d291c2e0a
https://git.kernel.org/stable/c/56b7a9d89c67932bf11b71e3b6d17941fc24a393
https://git.kernel.org/stable/c/108c46e8dacc4a0e472a74f98171115d49cbc079
https://git.kernel.org/stable/c/e1188332a9110cf3635fe286481ee38305b3c2b6
https://git.kernel.org/stable/c/70f4b78d560e592cbf3325b162424737d032fc1d
https://git.kernel.org/stable/c/a82b274697d0876b478594ca78ad1e6cb062467b
https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2026-98362
https://security-tracker.debian.org/tracker/CVE-2026-98362NoneNonehttps://git.kernel.org/linus/70f4b78d560e592cbf3325b162424737d032fc1d
http://www.cnnvd.org.cn/web/vulnerability/queryLds.tag?qcvCnnvdid=CVE-2026-98362
https://nvd.nist.gov/vuln/detail/CVE-2026-98362
https://ubuntu.com/security/CVE-2026-98362NoneNonehttps://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

likedislike
此处折叠了60条消息 查看更多
openeuler-ci-bot
openeuler-ci-bot成员
1 天前 评论:

source: @hulk-ci-bot

影响性分析说明:
In the Linux kernel, the following vulnerability has been resolved:

clk: scpi: bound-check DVFS index in scpi_dvfs_recalc_rate

dvfs_get_idx() may return an out-of-range index if the SCP firmware is
buggy or returns a stale value. Only negative indexes were rejected, so a
large index walked past info->opps and could treat garbage as a clock rate
(KASAN OOB / wrong frequency to consumers). The missing upper bound dates
back to the original SCPI clock driver.

Treat indexes >= opp count as invalid and return 0, same as idx < 0.

The Linux kernel CVE team has assigned CVE-2026-98362 to this issue.

openEuler评分:
9.8
AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/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:正常修复

likedislike
openeuler-ci-bot
openeuler-ci-bot成员
1 天前 评论:

经过cve-manager解析,部分字段填写错误,如红色字体所示:

影响性分析说明:
In the Linux kernel, the following vulnerability has been resolved:

clk: scpi: bound-check DVFS ind...

openEuler评分: (评分和向量)
(CVSS评分和矢量值不一致,请修改至矢量值和CVSS评分一致!)

受影响版本排查(受影响/不受影响):
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:正常修复

likedislike
openeuler-ci-botopeneuler-ci-bot成员
18 小时前 issue优先级由 无优先级 改变为 无优先级
openeuler-ci-bot
openeuler-ci-bot成员
18 小时前 评论:

source: @hulk-ci-bot

影响性分析说明:
In the Linux kernel, the following vulnerability has been resolved:

clk: scpi: bound-check DVFS index in scpi_dvfs_recalc_rate

dvfs_get_idx() may return an out-of-range index if the SCP firmware is
buggy or returns a stale value. Only negative indexes were rejected, so a
large index walked past info->opps and could treat garbage as a clock rate
(KASAN OOB / wrong frequency to consumers). The missing upper bound dates
back to the original SCPI clock driver.

Treat indexes >= opp count as invalid and return 0, same as idx < 0.

The Linux kernel CVE team has assigned CVE-2026-98362 to this issue.

openEuler评分:
9.8
AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/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:正常修复

likedislike
openeuler-ci-bot
openeuler-ci-bot成员
18 小时前 评论:

经过cve-manager解析,部分字段填写错误,如红色字体所示:

影响性分析说明:
In the Linux kernel, the following vulnerability has been resolved:

clk: scpi: bound-check DVFS ind...

openEuler评分: (评分和向量)
(CVSS评分和矢量值不一致,请修改至矢量值和CVSS评分一致!)

受影响版本排查(受影响/不受影响):
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:正常修复

likedislike