CVE-2026-98201-kernel-AtomGit

已开启

CVE-2026-98201 #19972

openeuler-ci-bot创建于 10月6日

10月6日创建

一、漏洞信息
漏洞编号：CVE-2026-98201
漏洞归属组件：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：N/A None
Vector：
漏洞简述：
In the Linux kernel, the following vulnerability has been resolved:Input: zero ff_effect before compat copy in input_ff_effect_from_userIn the compat path input_ff_effect_from_user() aliases the caller snative struct ff_effect with the smaller struct ff_effect_compat andcopies only the compat sized prefix: compat_effect = (struct ff_effect_compat *)effect; if (copy_from_user(compat_effect, buffer, sizeof(struct ff_effect_compat)))The tail of the native structure is never written. Callers pass anuninitialized on-stack object, for example evdev_do_ioctl() forEVIOCSFF, so those bytes keep their previous stack contents.input_ff_upload() then stores the full native structure inff->effects[id], from where a uinput based force feedback daemon canread it back via UI_BEGIN_FF_UPLOAD, disclosing kernel stack memory touserspace.Zero the effect before the compat copy.
漏洞公开时间：2026-10-06 18:08:02
漏洞创建时间：2026-10-06 17:39:44
漏洞详情参考链接：
https://nvd.nist.gov/vuln/detail/CVE-2026-98201

更多参考(点击展开)

参考来源	参考链接	来源链接
	https://lore.kernel.org/linux-cve-announce/2026100637-CVE-2026-98201-6ff8@gregkh/T/#u
	https://git.kernel.org/stable/c/b878720e8bcaa4cf7163a5081f904dd6baf11b2c
	https://git.kernel.org/stable/c/0d05b43b55d4784a42ce8fb318175f8ad7d9af5a
	https://git.kernel.org/stable/c/ed0406e490f48ed180df140fe2a81be26bccb1a9
	https://git.kernel.org/stable/c/f84819ef8d66931ee3998fee3c4f03230f4cb6cc
	https://git.kernel.org/stable/c/ed0905fda39682d3da7937184397d3276abbffa8
	https://git.kernel.org/stable/c/c5e573bb095d502be7cbbaa99c26a20984111c6d
	https://git.kernel.org/stable/c/ec174c2ab1abb76b20fa167c6db848c3d97aa838
	https://git.kernel.org/stable/c/6c26681c5668c973bd0e951407d670ac60d9cd66

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

详情(点击展开)

影响的包	修复版本	修复补丁	问题引入补丁	来源
		https://git.kernel.org/stable/c/b878720e8bcaa4cf7163a5081f904dd6baf11b2c		cybersecurity
		https://git.kernel.org/stable/c/0d05b43b55d4784a42ce8fb318175f8ad7d9af5a		cybersecurity
		https://git.kernel.org/stable/c/ed0406e490f48ed180df140fe2a81be26bccb1a9		cybersecurity
		https://git.kernel.org/stable/c/f84819ef8d66931ee3998fee3c4f03230f4cb6cc		cybersecurity
		https://git.kernel.org/stable/c/ed0905fda39682d3da7937184397d3276abbffa8		vuldb
		https://git.kernel.org/stable/c/c5e573bb095d502be7cbbaa99c26a20984111c6d		cybersecurity
		https://git.kernel.org/stable/c/ec174c2ab1abb76b20fa167c6db848c3d97aa838		cybersecurity
		https://git.kernel.org/stable/c/6c26681c5668c973bd0e951407d670ac60d9cd66		cybersecurity

二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:Input: zero ff_effect before compat copy in input_ff_effect_from_userIn the compat path input_ff_effect_from_user() aliases the caller'snative struct ff_effect with the smaller struct ff_effect_compat andcopies only the compat sized prefix: compat_effect = (struct ff_effect_compat *)effect; if (copy_from_user(compat_effect, buffer, sizeof(struct ff_effect_compat)))The tail of the native structure is never written. Callers pass anuninitialized on-stack object, for example evdev_do_ioctl() forEVIOCSFF, so those bytes keep their previous stack contents.input_ff_upload() then stores the full native structure inff->effects[id], from where a uinput based force feedback daemon canread it back via UI_BEGIN_FF_UPLOAD, disclosing kernel stack memory touserspace.Zero the effect before the compat copy.The Linux kernel CVE team has assigned CVE-2026-98201 to this issue.
openEuler评分：
3.3
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):正常修复

openeuler-ci-bot成员

10月6日添加了label：CVE/UNFIXED

openeuler-ci-bot成员

10月6日评论：

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

openeuler-ci-bot成员

10月6日将 wkfxxx、openeuler-ci-bot、zeng_zhaorong、sanglipeng、oekernel、hanjunguo 设为负责人

openeuler-ci-bot成员

10月6日添加了label：sig/Kernel

openeuler-ci-bot成员

10月6日评论：

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: 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, @chenxiaosonggitcode, @chiqijun, @chizl, @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, @hygmm, @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, @sageDriver, @sanglipeng, @shu-shengming, @shuaijiakun, @sinat_17738335, @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 .

此处折叠了75条消息查看更多

openeuler-ci-bot成员

1 天前评论：

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

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

Input: zero ff_effect before co...

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:正常修复

openeuler-ci-bot成员

20 小时前 issue优先级由无优先级改变为无优先级

openeuler-ci-bot成员

20 小时前修改了issue 的描述

openeuler-ci-bot成员

20 小时前评论：

source: @hulk-ci-bot

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

Input: zero ff_effect before compat copy in input_ff_effect_from_user

In the compat path input_ff_effect_from_user() aliases the caller's
native struct ff_effect with the smaller struct ff_effect_compat and
copies only the compat sized prefix:

compat_effect = (struct ff_effect_compat *)effect;

if (copy_from_user(compat_effect, buffer,
		   sizeof(struct ff_effect_compat)))

The tail of the native structure is never written. Callers pass an
uninitialized on-stack object, for example evdev_do_ioctl() for
EVIOCSFF, so those bytes keep their previous stack contents.
input_ff_upload() then stores the full native structure in
ff->effects[id], from where a uinput based force feedback daemon can
read it back via UI_BEGIN_FF_UPLOAD, disclosing kernel stack memory to
userspace.

Zero the effect before the compat copy.

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

openEuler评分：
3.3
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:受影响

openeuler-ci-bot成员

20 小时前评论：

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

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

Input: zero ff_effect before co...

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