已开启
CVE-2026-64363 #16659
openeuler-ci-bot创建于  7月26日
openeuler-ci-bot
openeuler-ci-bot成员
7月26日 创建

一、漏洞信息
漏洞编号:CVE-2026-64363
漏洞归属组件:kernel
漏洞归属的版本:4.19.140,4.19.194,4.19.90,5.10.0,6.1.19,6.12.33,6.18.18,6.4.0,6.6.0
CVSS评分:
BaseScore:7.8 High
Vector:CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
漏洞简述:
In the Linux kernel, the following vulnerability has been resolved:HID: appleir: fix UAF on pending key_up_timer in remove()appleir_remove() runs hid_hw_stop() before timer_delete_sync().hid_hw_stop() synchronously unregisters the HID input device viahid_disconnect() -> hidinput_disconnect() -> input_unregister_device(),which drops the last reference and frees the underlying input_dev whenno userspace handle holds it open.key_up_tick() reads appleir->input_dev and calls input_report_key() /input_sync() on it. The timer is armed from appleir_raw_event() witha HZ/8 (~125 ms) timeout on every keydown and key-repeat report. If akey was pressed shortly before the device is disconnected, the timercan fire after hid_hw_stop() has freed input_dev but before theteardown drains it.A simple reorder is not sufficient. Putting the timer drain firststill leaves a window where a USB URB completion (raw_event) runningduring hid_hw_stop() can call mod_timer() and re-arm the timer, whichthen fires after hidinput_disconnect() has freed input_dev. The sameURB-completion window also lets raw_event() reach key_up(), key_down()and battery_flat() directly, all of which dereferenceappleir->input_dev.Introduce a removing flag on struct appleir, gated by the existingspinlock. appleir_remove() sets the flag under the lock and thenshuts down the timer with timer_shutdown_sync(), which both drains anyin-flight callback and permanently disables further mod_timer() calls.appleir_raw_event() and key_up_tick() bail out early if the flag isset, so no path can arm or run the timer, or dereferenceappleir->input_dev, after remove() has started tearing down.The keyrepeat and flatbattery branches of appleir_raw_event()previously called into the input layer without holding the spinlock;take it now so the flag check is well-defined. This incidentallycloses a pre-existing read-side race on appleir->current_key in thekeyrepeat branch.This bug is structurally a sibling of commit 4db2af929279 ( HID:appletb-kbd: fix UAF in inactivity-timer cleanup path ) and has beenpresent since the driver was introduced.
漏洞公开时间:2026-07-25 18:17:18
漏洞创建时间:2026-07-26 01:46:21
漏洞详情参考链接:
https://nvd.nist.gov/vuln/detail/CVE-2026-64363

更多参考(点击展开)
参考来源 参考链接 来源链接
https://nvd.nist.gov/vuln/detail/CVE-2026-64363
https://lore.kernel.org/linux-cve-announce/2026072521-CVE-2026-64363-cff0@gregkh/T
https://git.kernel.org/stable/c/b363d964ca829c1761c9f04188dfa28f90b0f2d4
https://git.kernel.org/stable/c/6b0838e86da88b1d3bff86f19761ff25af73eaca
https://git.kernel.org/stable/c/3755f6e25776b8b12ddf062f9b573f05090e4034
https://bugzilla.redhat.com/show_bug.cgi?id=2507281
https://git.kernel.org/stable/c/75fe87e19d8aff81eb2c64d15d244ab8da4de945
https://security-tracker.debian.org/tracker/CVE-2026-64363
https://lore.kernel.org/linux-cve-announce/2026072521-CVE-2026-64363-cff0@gregkh/T/#u
https://git.kernel.org/stable/c/3d30a0bb0e79621ae921b487835c56198adfafa3
https://git.kernel.org/stable/c/37a52c61d4f78153c38ae1f7491dfcc8ac828dcf
https://git.kernel.org/stable/c/05e3decc55d1deca9410e0eb36466651fcbe57a5
https://git.kernel.org/stable/c/89ef67359672bf4cd6921524e39f61648fe38c0f
https://www.cve.org/CVERecord?id=CVE-2026-64363

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

详情(点击展开)
影响的包 修复版本 修复补丁 问题引入补丁 来源
gregkh/linux https://git.kernel.org/stable/c/89ef67359672bf4cd6921524e39f61648fe38c0f ljqc
gregkh/linux https://git.kernel.org/stable/c/3d30a0bb0e79621ae921b487835c56198adfafa3 ljqc
gregkh/linux https://git.kernel.org/stable/c/37a52c61d4f78153c38ae1f7491dfcc8ac828dcf ljqc
gregkh/linux https://git.kernel.org/stable/c/05e3decc55d1deca9410e0eb36466651fcbe57a5 ljqc
gregkh/linux https://git.kernel.org/stable/c/3755f6e25776b8b12ddf062f9b573f05090e4034 ljqc
gregkh/linux https://git.kernel.org/stable/c/b363d964ca829c1761c9f04188dfa28f90b0f2d4 ljqc
gregkh/linux https://git.kernel.org/stable/c/6b0838e86da88b1d3bff86f19761ff25af73eaca ljqc
gregkh/linux https://git.kernel.org/stable/c/75fe87e19d8aff81eb2c64d15d244ab8da4de945 ljqc
https://git.kernel.org/stable/c/b363d964ca829c1761c9f04188dfa28f90b0f2d4 cvelistv5
https://git.kernel.org/stable/c/6b0838e86da88b1d3bff86f19761ff25af73eaca cvelistv5
https://git.kernel.org/stable/c/3755f6e25776b8b12ddf062f9b573f05090e4034 cvelistv5
https://git.kernel.org/stable/c/75fe87e19d8aff81eb2c64d15d244ab8da4de945 cvelistv5
https://git.kernel.org/stable/c/3d30a0bb0e79621ae921b487835c56198adfafa3 cvelistv5
https://git.kernel.org/stable/c/37a52c61d4f78153c38ae1f7491dfcc8ac828dcf cvelistv5
https://git.kernel.org/stable/c/05e3decc55d1deca9410e0eb36466651fcbe57a5 cvelistv5
https://git.kernel.org/stable/c/89ef67359672bf4cd6921524e39f61648fe38c0f cvelistv5

二、漏洞分析结构反馈
影响性分析说明:
In the Linux kernel, the following vulnerability has been resolved:HID: appleir: fix UAF on pending key_up_timer in remove()appleir_remove() runs hid_hw_stop() before timer_delete_sync().hid_hw_stop() synchronously unregisters the HID input device viahid_disconnect() -> hidinput_disconnect() -> input_unregister_device(),which drops the last reference and frees the underlying input_dev whenno userspace handle holds it open.key_up_tick() reads appleir->input_dev and calls input_report_key() /input_sync() on it. The timer is armed from appleir_raw_event() witha HZ/8 (~125 ms) timeout on every keydown and key-repeat report. If akey was pressed shortly before the device is disconnected, the timercan fire after hid_hw_stop() has freed input_dev but before theteardown drains it.A simple reorder is not sufficient. Putting the timer drain firststill leaves a window where a USB URB completion (raw_event) runningduring hid_hw_stop() can call mod_timer() and re-arm the timer, whichthen fires after hidinput_disconnect() has freed input_dev. The sameURB-completion window also lets raw_event() reach key_up(), key_down()and battery_flat() directly, all of which dereferenceappleir->input_dev.Introduce a removing flag on struct appleir, gated by the existingspinlock. appleir_remove() sets the flag under the lock and thenshuts down the timer with timer_shutdown_sync(), which both drains anyin-flight callback and permanently disables further mod_timer() calls.appleir_raw_event() and key_up_tick() bail out early if the flag isset, so no path can arm or run the timer, or dereferenceappleir->input_dev, after remove() has started tearing down.The keyrepeat and flatbattery branches of appleir_raw_event()previously called into the input layer without holding the spinlock;take it now so the flag check is well-defined. This incidentallycloses a pre-existing read-side race on appleir->current_key in thekeyrepeat branch.This bug is structurally a sibling of commit 4db2af929279 ( HID:appletb-kbd: fix UAF in inactivity-timer cleanup path ) and has beenpresent since the driver was introduced.
openEuler评分:
7.8
Vector:CVSS:3.1/AV:L/AC:L/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-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(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):否
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(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):正常修复
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):正常修复

likedislike
openeuler-ci-botopeneuler-ci-bot成员
7月26日 添加了label:CVE/UNFIXED
openeuler-ci-bot
openeuler-ci-bot成员
7月26日 评论:

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


影响性分析说明:

openEuler评分: (评分和向量)

受影响版本排查(受影响/不受影响):
1.master(6.18.18):
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.18):
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.18):
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
devstation-robot
devstation-robot
7月26日 评论:

检测到新建 CVE Issue,CVE-ID: CVE-2026-64363。

你可以通过以下两种方式使用 CVE 修复服务:

  1. 分支影响分析

    • 在本 Issue 下评论:/analysis_branches
    • 系统将自动分析各个分支是否受影响,并在本 Issue 下给出表格形式的分析结果;
  2. 在指定分支上创建 PR(修复提交)

    • 在本 Issue 下按如下格式评论(字段均为必填,每个字段单独一行):
/create_pr

branch: OLK-6.6 OLK-5.10
name: dev
email: dev@devstation.com
backport-engine: mystique
  • 说明:
    • branch: 需要创建 PR 的目标分支列表,例如 OLK-6.6 OLK-5.10;
    • name: PR 签名人姓名(如责任人或安全负责人);
    • email: PR 签名人邮箱;
    • backport-engine(可选): 回移植引擎,可设为 mystique 切换迁移方案,不填则使用默认引擎;

系统会根据上述信息自动在指定分支上创建 PR,并在本 Issue 下反馈结果。

provided by DevStation.

likedislike
openeuler-ci-bot
openeuler-ci-bot成员
7月26日 评论:
参考网址 关联pr 状态 补丁链接
https://www.opencve.io/cve/CVE-2026-64363NoneNonehttps://git.kernel.org/stable/c/89ef67359672bf4cd6921524e39f61648fe38c0f
https://git.kernel.org/stable/c/3d30a0bb0e79621ae921b487835c56198adfafa3
https://git.kernel.org/stable/c/05e3decc55d1deca9410e0eb36466651fcbe57a5
https://git.kernel.org/stable/c/37a52c61d4f78153c38ae1f7491dfcc8ac828dcf
https://git.kernel.org/stable/c/75fe87e19d8aff81eb2c64d15d244ab8da4de945
https://git.kernel.org/stable/c/b363d964ca829c1761c9f04188dfa28f90b0f2d4
https://git.kernel.org/stable/c/6b0838e86da88b1d3bff86f19761ff25af73eaca
https://git.kernel.org/stable/c/3755f6e25776b8b12ddf062f9b573f05090e4034
https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2026-64363
https://security-tracker.debian.org/tracker/CVE-2026-64363NoneNonehttps://git.kernel.org/linus/75fe87e19d8aff81eb2c64d15d244ab8da4de945
http://www.cnnvd.org.cn/web/vulnerability/queryLds.tag?qcvCnnvdid=CVE-2026-64363
https://nvd.nist.gov/vuln/detail/CVE-2026-64363NoneNonehttps://git.kernel.org/stable/c/89ef67359672bf4cd6921524e39f61648fe38c0f
https://git.kernel.org/stable/c/3d30a0bb0e79621ae921b487835c56198adfafa3
https://git.kernel.org/stable/c/05e3decc55d1deca9410e0eb36466651fcbe57a5
https://git.kernel.org/stable/c/37a52c61d4f78153c38ae1f7491dfcc8ac828dcf
https://git.kernel.org/stable/c/75fe87e19d8aff81eb2c64d15d244ab8da4de945
https://git.kernel.org/stable/c/b363d964ca829c1761c9f04188dfa28f90b0f2d4
https://git.kernel.org/stable/c/6b0838e86da88b1d3bff86f19761ff25af73eaca
https://git.kernel.org/stable/c/3755f6e25776b8b12ddf062f9b573f05090e4034
https://ubuntu.com/security/CVE-2026-64363

说明:补丁链接仅供初步排查参考,实际可用性请人工再次确认,补丁下载验证可使用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
openeuler-ci-botopeneuler-ci-bot成员
7月26日 添加了label:sig/Kernel
此处折叠了44条消息 查看更多
openeuler-ci-bot
openeuler-ci-bot成员
9月15日 评论:

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

状态 分析项目 内容
已分析 1.影响性分析说明 In the Linux kernel, the following vulnerability has been resolved:HID: appleir: fix UAF on pending key_up_timer in remove()appleir_remove() runs hid_hw_stop() before timer_delete_sync().hid_hw_stop() synchronously unregisters the HID input device viahid_disconnect() -> hidinput_disconnect() -> input_unregister_device(),which drops the last reference and frees the underlying input_dev whenno userspace handle holds it open.key_up_tick() reads appleir->input_dev and calls input_report_key() /input_sync() on it. The timer is armed from appleir_raw_event() witha HZ/8 (~125 ms) timeout on every keydown and key-repeat report. If akey was pressed shortly before the device is disconnected, the timercan fire after hid_hw_stop() has freed input_dev but before theteardown drains it.A simple reorder is not sufficient. Putting the timer drain firststill leaves a window where a USB URB completion (raw_event) runningduring hid_hw_stop() can call mod_timer() and re-arm the timer, whichthen fires after hidinput_disconnect() has freed input_dev. The sameURB-completion window also lets raw_event() reach key_up(), key_down()and battery_flat() directly, all of which dereferenceappleir->input_dev.Introduce a 'removing' flag on struct appleir, gated by the existingspinlock. appleir_remove() sets the flag under the lock and thenshuts down the timer with timer_shutdown_sync(), which both drains anyin-flight callback and permanently disables further mod_timer() calls.appleir_raw_event() and key_up_tick() bail out early if the flag isset, so no path can arm or run the timer, or dereferenceappleir->input_dev, after remove() has started tearing down.The keyrepeat and flatbattery branches of appleir_raw_event()previously called into the input layer without holding the spinlock;take it now so the flag check is well-defined. This incidentallycloses a pre-existing read-side race on appleir->current_key in thekeyrepeat branch.This bug is structurally a sibling of commit 4db2af929279 ("HID:appletb-kbd: fix UAF in inactivity-timer cleanup path") and has beenpresent since the driver was introduced.
已分析 2.openEulerScore 7.8
已分析 3.openEulerVector AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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:正常修复

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

likedislike
openeuler-ci-bot
openeuler-ci-bot成员
9月15日 评论:

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

原因说明:
1.master:不受影响-漏洞代码不能被攻击者触发
2.openEuler-20.03-LTS-SP4:正常修复(PR未合入)
3.openEuler-22.03-LTS-SP4:正常修复(PR未合入)
4.openEuler-24.03-LTS-Next:不受影响-漏洞代码不能被攻击者触发
5.openEuler-24.03-LTS-SP1:正常修复(PR未合入)
6.openEuler-24.03-LTS-SP3:正常修复(PR未合入)
7.openEuler-24.03-LTS-SP4:正常修复(PR未合入)
8.openEuler-22.03-LTS-SP3:正常修复(PR未合入)
9.openEuler-24.03-LTS:正常修复(PR未合入)
10.openEuler-24.03-LTS-SP2:正常修复(PR未合入)

likedislike
LLiu Rui
9月15日 关联了pull request:[OLK-5.10] Fix CVE-2026-64363
LLiu Rui
9月15日 关联了pull request:[openEuler-1.0-LTS] Fix CVE-2026-64363
openeuler-ci-botopeneuler-ci-bot成员
9月16日 修改了issue 的描述