Open
CVE-2026-63960 #16287
openeuler-ci-botAdd on  Jul 20
openeuler-ci-bot
openeuler-ci-botCollaborators
Jul 20 Create

一、漏洞信息
漏洞编号:CVE-2026-63960
漏洞归属组件: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:5.5 Medium
Vector:CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
漏洞简述:
In the Linux kernel, the following vulnerability has been resolved:usb: typec: wcove: don t write past struct pd_message in wcove_read_rx_buffer()wcove_read_rx_buffer() copies the PD RX FIFO into the caller sstruct pd_message with for (i = 0; i < USBC_RXINFO_RXBYTES(info); i++) regmap_read(wcove->regmap, USBC_RX_DATA + i, msg + i);which has two problems:USBC_RXINFO_RXBYTES() is a 5-bit field (max 31) while struct pd_messageis 30 bytes (__le16 header + __le32 payload[PD_MAX_PAYLOAD], packed).The byte count latched in RXINFO is the number of bytes the port partnerput on the wire, so a malicious partner that transmits a 31-byte framecan drive the loop one byte past the destination if the WCOVE BMCreceiver does not enforce the PD object-count limit in hardware. Theexisting FIXME flagged this as unverified.Independently, regmap_read() takes an unsigned int * and stores a fullunsigned int at the destination. Passing the byte pointer msg + i meanseach iteration writes four bytes; the high three are zero (val_bits is8) and are normally overwritten by the next iteration, but the finaliteration s high bytes are not. With RXBYTES == 30 the i == 29 iterationalready writes three zero bytes past msg, which sits on the IRQ thread sstack in wcove_typec_irq().Clamp the loop to sizeof(struct pd_message) and read each register intoa local before storing only its low byte, so the copy can never exceedthe destination regardless of what RXINFO reports.
漏洞公开时间:2026-07-20 00:17:14
漏洞创建时间:2026-07-20 11:17:06
漏洞详情参考链接:
https://nvd.nist.gov/vuln/detail/CVE-2026-63960

更多参考(点击展开)
参考来源 参考链接 来源链接
https://nvd.nist.gov/vuln/detail/CVE-2026-63960
https://git.kernel.org/stable/c/4af7ad0e6d7aa4403dbb1dac7b9659b0421efcaa
https://lore.kernel.org/linux-cve-announce/2026071957-CVE-2026-63960-990c@gregkh/T
https://git.kernel.org/stable/c/e94933dc41b87503bf585c8c6d53d740620eceb9
https://git.kernel.org/stable/c/3f9d50c8b02b4af0646aa892465080f9061fc89c
https://git.kernel.org/stable/c/6899f5b6d7b83ce79a3d331dc61dd31bf73f9c22
https://git.kernel.org/stable/c/f2a1edc0bd142edabc6c85d88713f2bc178dd317
https://bugzilla.redhat.com/show_bug.cgi?id=2502381
https://git.kernel.org/stable/c/3e632098d0521257ea965bbd6fde807d9bee5c8a
https://git.kernel.org/stable/c/d0e4b8b3c6b7607a16932556eaaca5d5cf69f192
https://git.kernel.org/stable/c/5cd0e7ac4eefbdb330f8c72694fe74e63df65552
https://www.cve.org/CVERecord?id=CVE-2026-63960

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

详情(点击展开)
影响的包 修复版本 修复补丁 问题引入补丁 来源
gregkh/linux https://git.kernel.org/stable/c/3e632098d0521257ea965bbd6fde807d9bee5c8a ljqc
gregkh/linux https://git.kernel.org/stable/c/f2a1edc0bd142edabc6c85d88713f2bc178dd317 ljqc
gregkh/linux https://git.kernel.org/stable/c/6899f5b6d7b83ce79a3d331dc61dd31bf73f9c22 ljqc
gregkh/linux https://git.kernel.org/stable/c/5cd0e7ac4eefbdb330f8c72694fe74e63df65552 ljqc
gregkh/linux https://git.kernel.org/stable/c/d0e4b8b3c6b7607a16932556eaaca5d5cf69f192 ljqc
gregkh/linux https://git.kernel.org/stable/c/e94933dc41b87503bf585c8c6d53d740620eceb9 ljqc
gregkh/linux https://git.kernel.org/stable/c/3f9d50c8b02b4af0646aa892465080f9061fc89c ljqc
gregkh/linux https://git.kernel.org/stable/c/4af7ad0e6d7aa4403dbb1dac7b9659b0421efcaa ljqc
https://git.kernel.org/stable/c/4af7ad0e6d7aa4403dbb1dac7b9659b0421efcaa cvelistv5
https://git.kernel.org/stable/c/e94933dc41b87503bf585c8c6d53d740620eceb9 cvelistv5
https://git.kernel.org/stable/c/3f9d50c8b02b4af0646aa892465080f9061fc89c cvelistv5
https://git.kernel.org/stable/c/6899f5b6d7b83ce79a3d331dc61dd31bf73f9c22 cvelistv5
https://git.kernel.org/stable/c/f2a1edc0bd142edabc6c85d88713f2bc178dd317 cvelistv5
https://git.kernel.org/stable/c/3e632098d0521257ea965bbd6fde807d9bee5c8a cvelistv5
https://git.kernel.org/stable/c/d0e4b8b3c6b7607a16932556eaaca5d5cf69f192 cvelistv5
https://git.kernel.org/stable/c/5cd0e7ac4eefbdb330f8c72694fe74e63df65552 cvelistv5

二、漏洞分析结构反馈
影响性分析说明:
In the Linux kernel, the following vulnerability has been resolved:usb: typec: wcove: don't write past struct pd_message in wcove_read_rx_buffer()wcove_read_rx_buffer() copies the PD RX FIFO into the caller'sstruct pd_message with for (i = 0; i < USBC_RXINFO_RXBYTES(info); i++) regmap_read(wcove->regmap, USBC_RX_DATA + i, msg + i);which has two problems:USBC_RXINFO_RXBYTES() is a 5-bit field (max 31) while struct pd_messageis 30 bytes (__le16 header + __le32 payload[PD_MAX_PAYLOAD], packed).The byte count latched in RXINFO is the number of bytes the port partnerput on the wire, so a malicious partner that transmits a 31-byte framecan drive the loop one byte past the destination if the WCOVE BMCreceiver does not enforce the PD object-count limit in hardware. Theexisting FIXME flagged this as unverified.Independently, regmap_read() takes an unsigned int * and stores a fullunsigned int at the destination. Passing the byte pointer msg + i meanseach iteration writes four bytes; the high three are zero (val_bits is8) and are normally overwritten by the next iteration, but the finaliteration's high bytes are not. With RXBYTES == 30 the i == 29 iterationalready writes three zero bytes past msg, which sits on the IRQ thread'sstack in wcove_typec_irq().Clamp the loop to sizeof(struct pd_message) and read each register intoa local before storing only its low byte, so the copy can never exceedthe destination regardless of what RXINFO reports.The Linux kernel CVE team has assigned CVE-2026-63960 to this issue.
openEuler评分:
5.5
Vector:CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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):应源码修复-openEuler社区发布软件包不受影响
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):应源码修复-openEuler社区发布软件包不受影响
8.openEuler-24.03-LTS-SP2(6.6.0):不修复-超出修复范围
9.openEuler-24.03-LTS-SP3(6.6.0):应源码修复-openEuler社区发布软件包不受影响
10.openEuler-24.03-LTS-SP4(6.6.0):应源码修复-openEuler社区发布软件包不受影响

likedislike
openeuler-ci-botopeneuler-ci-botCollaborators
Jul 20 Added label: CVE/UNFIXED
openeuler-ci-bot
openeuler-ci-botCollaborators
Jul 20 Comments:

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
Jul 20 Comments:

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

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

  1. 分支影响分析

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

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

branch: OLK-6.6 OLK-5.10
name: dev
email: dev@devstation.com
  • 说明:
    • branch: 需要创建 PR 的目标分支列表,例如 OLK-6.6 OLK-5.10;
    • name: PR 签名人姓名(如责任人或安全负责人);
    • email: PR 签名人邮箱;

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

provided by DevStation.

likedislike
openeuler-ci-botopeneuler-ci-botCollaborators
Jul 20 Added label: sig/Kernel
openeuler-ci-bot
openeuler-ci-botCollaborators
Jul 20 Comments:

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.

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, @allen-shi, @baratta, @bibo_mao, @caixu-blue, @chen-jun-hw, @chenjiesong, @chenjunxin1992, @chenke2026, @chiqijun, @chriszjh, @duanqiangwen, @eingesch, @fangfeng123, @fanghaiqinghw, @gaojuxin09, @gouhao2022, @guohaocs2c, @guzitao, @hanjunguo, @hanliyang, @hellotcc, @henryze, @hewanhan, @hjx_gitff, @hongbo-lee, @hongwu-wang, @htforge, @hu-chunzhi, @hunan4222, @jackknight, @jerry_lilijun, @jiayi0118, @junlong-zheng, @juntianlinux, @kailiu42, @kaitiandu, @kazero00, @kevinzhu1, @kile2009, @koishimind, @kongzizaixian, @kylin-mayukun, @leoliu-oc, @li-huisong, @linan888, @linyunsheng, @liulongfang, @liyihang0226, @lostway1, @lujialin2, @mao-hongbo, @markyuan4ta21, @mawupeng, @mingqian218472, @mingrui-liu, @mufengyan, @pigalsofine, @robinorg, @rock_hw, @sanglipeng, @shu-shengming, @shuaijiakun, @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 .

likedislike
openeuler-ci-bot
openeuler-ci-botCollaborators
Jul 20 Comments:
参考网址 关联pr 状态 补丁链接
https://www.opencve.io/cve/CVE-2026-63960NoneNonehttps://git.kernel.org/stable/c/6899f5b6d7b83ce79a3d331dc61dd31bf73f9c22
https://git.kernel.org/stable/c/e94933dc41b87503bf585c8c6d53d740620eceb9
https://git.kernel.org/stable/c/3e632098d0521257ea965bbd6fde807d9bee5c8a
https://git.kernel.org/stable/c/3f9d50c8b02b4af0646aa892465080f9061fc89c
https://git.kernel.org/stable/c/f2a1edc0bd142edabc6c85d88713f2bc178dd317
https://git.kernel.org/stable/c/5cd0e7ac4eefbdb330f8c72694fe74e63df65552
https://git.kernel.org/stable/c/d0e4b8b3c6b7607a16932556eaaca5d5cf69f192
https://git.kernel.org/stable/c/4af7ad0e6d7aa4403dbb1dac7b9659b0421efcaa
https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2026-63960
https://security-tracker.debian.org/tracker/CVE-2026-63960NoneNonehttps://git.kernel.org/linus/4af7ad0e6d7aa4403dbb1dac7b9659b0421efcaa
http://www.cnnvd.org.cn/web/vulnerability/queryLds.tag?qcvCnnvdid=CVE-2026-63960
https://nvd.nist.gov/vuln/detail/CVE-2026-63960NoneNonehttps://git.kernel.org/stable/c/6899f5b6d7b83ce79a3d331dc61dd31bf73f9c22
https://git.kernel.org/stable/c/e94933dc41b87503bf585c8c6d53d740620eceb9
https://git.kernel.org/stable/c/3e632098d0521257ea965bbd6fde807d9bee5c8a
https://git.kernel.org/stable/c/3f9d50c8b02b4af0646aa892465080f9061fc89c
https://git.kernel.org/stable/c/f2a1edc0bd142edabc6c85d88713f2bc178dd317
https://git.kernel.org/stable/c/5cd0e7ac4eefbdb330f8c72694fe74e63df65552
https://git.kernel.org/stable/c/d0e4b8b3c6b7607a16932556eaaca5d5cf69f192
https://git.kernel.org/stable/c/4af7ad0e6d7aa4403dbb1dac7b9659b0421efcaa
https://ubuntu.com/security/CVE-2026-63960NoneNonehttps://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
hulk-ci-botCollaborators
Jul 20 Comments:

CVE-2026-63960

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

usb: typec: wcove: don't write past struct pd_message in wcove_read_rx_buffer()

wcove_read_rx_buffer() copies the PD RX FIFO into the caller's
struct pd_message with

for (i = 0; i &lt; USBC_RXINFO_RXBYTES(info); i++)
	regmap_read(wcove-&gt;regmap, USBC_RX_DATA + i, msg + i);

which has two problems:

USBC_RXINFO_RXBYTES() is a 5-bit field (max 31) while struct pd_message
is 30 bytes (__le16 header + __le32 payload[PD_MAX_PAYLOAD], packed).
The byte count latched in RXINFO is the number of bytes the port partner
put on the wire, so a malicious partner that transmits a 31-byte frame
can drive the loop one byte past the destination if the WCOVE BMC
receiver does not enforce the PD object-count limit in hardware. The
existing FIXME flagged this as unverified.

Independently, regmap_read() takes an unsigned int * and stores a full
unsigned int at the destination. Passing the byte pointer msg + i means
each iteration writes four bytes; the high three are zero (val_bits is
8) and are normally overwritten by the next iteration, but the final
iteration's high bytes are not. With RXBYTES == 30 the i == 29 iteration
already writes three zero bytes past msg, which sits on the IRQ thread's
stack in wcove_typec_irq().

Clamp the loop to sizeof(struct pd_message) and read each register into
a local before storing only its low byte, so the copy can never exceed
the destination regardless of what RXINFO reports.

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

openEuler评分:(评分和向量)
3.9
CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:L/I:L/A:L

受影响版本排查(受影响/不受影响):
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-botCollaborators
Jul 20 Modify description of issue
openeuler-ci-bot
openeuler-ci-botCollaborators
Jul 20 Comments:

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

状态 分析项目 内容
已分析 1.影响性分析说明 In the Linux kernel, the following vulnerability has been resolved:usb: typec: wcove: don't write past struct pd_message in wcove_read_rx_buffer()wcove_read_rx_buffer() copies the PD RX FIFO into the caller'sstruct pd_message withfor (i = 0; i < USBC_RXINFO_RXBYTES(info); i++)regmap_read(wcove->regmap, USBC_RX_DATA + i, msg + i);which has two problems:USBC_RXINFO_RXBYTES() is a 5-bit field (max 31) while struct pd_messageis 30 bytes (__le16 header + __le32 payload[PD_MAX_PAYLOAD], packed).The byte count latched in RXINFO is the number of bytes the port partnerput on the wire, so a malicious partner that transmits a 31-byte framecan drive the loop one byte past the destination if the WCOVE BMCreceiver does not enforce the PD object-count limit in hardware. Theexisting FIXME flagged this as unverified.Independently, regmap_read() takes an unsigned int * and stores a fullunsigned int at the destination. Passing the byte pointer msg + i meanseach iteration writes four bytes; the high three are zero (val_bits is8) and are normally overwritten by the next iteration, but the finaliteration's high bytes are not. With RXBYTES == 30 the i == 29 iterationalready writes three zero bytes past msg, which sits on the IRQ thread'sstack in wcove_typec_irq().Clamp the loop to sizeof(struct pd_message) and read each register intoa local before storing only its low byte, so the copy can never exceedthe destination regardless of what RXINFO reports.The Linux kernel CVE team has assigned CVE-2026-63960 to this issue.
已分析 2.openEulerScore 3.9
已分析 3.openEulerVector AV:L/AC:H/PR:H/UI:N/S:U/C:L/I:L/A:L
已分析 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-botopeneuler-ci-botCollaborators
Jul 20 changed custom state from 待办的 to 进行中
openeuler-ci-botopeneuler-ci-botCollaborators
Jul 21 Modify description of issue
openeuler-ci-botopeneuler-ci-botCollaborators
Jul 24 Modify description of issue
openeuler-ci-botopeneuler-ci-botCollaborators
Jul 25 Modify description of issue
hulk-ci-botCollaborators
Jul 27 Comments:

CVE-2026-63960

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

usb: typec: wcove: don't write past struct pd_message in wcove_read_rx_buffer()

wcove_read_rx_buffer() copies the PD RX FIFO into the caller's
struct pd_message with

for (i = 0; i &lt; USBC_RXINFO_RXBYTES(info); i++)
	regmap_read(wcove-&gt;regmap, USBC_RX_DATA + i, msg + i);

which has two problems:

USBC_RXINFO_RXBYTES() is a 5-bit field (max 31) while struct pd_message
is 30 bytes (__le16 header + __le32 payload[PD_MAX_PAYLOAD], packed).
The byte count latched in RXINFO is the number of bytes the port partner
put on the wire, so a malicious partner that transmits a 31-byte frame
can drive the loop one byte past the destination if the WCOVE BMC
receiver does not enforce the PD object-count limit in hardware. The
existing FIXME flagged this as unverified.

Independently, regmap_read() takes an unsigned int * and stores a full
unsigned int at the destination. Passing the byte pointer msg + i means
each iteration writes four bytes; the high three are zero (val_bits is
8) and are normally overwritten by the next iteration, but the final
iteration's high bytes are not. With RXBYTES == 30 the i == 29 iteration
already writes three zero bytes past msg, which sits on the IRQ thread's
stack in wcove_typec_irq().

Clamp the loop to sizeof(struct pd_message) and read each register into
a local before storing only its low byte, so the copy can never exceed
the destination regardless of what RXINFO reports.

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

openEuler评分:(评分和向量)
6.8
CVSS:3.1/AV:P/AC:L/PR:N/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-botopeneuler-ci-botCollaborators
Jul 27 Modify description of issue
openeuler-ci-bot
openeuler-ci-botCollaborators
Jul 27 Comments:

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

状态 分析项目 内容
已分析 1.影响性分析说明 In the Linux kernel, the following vulnerability has been resolved:usb: typec: wcove: don't write past struct pd_message in wcove_read_rx_buffer()wcove_read_rx_buffer() copies the PD RX FIFO into the caller'sstruct pd_message withfor (i = 0; i < USBC_RXINFO_RXBYTES(info); i++)regmap_read(wcove->regmap, USBC_RX_DATA + i, msg + i);which has two problems:USBC_RXINFO_RXBYTES() is a 5-bit field (max 31) while struct pd_messageis 30 bytes (__le16 header + __le32 payload[PD_MAX_PAYLOAD], packed).The byte count latched in RXINFO is the number of bytes the port partnerput on the wire, so a malicious partner that transmits a 31-byte framecan drive the loop one byte past the destination if the WCOVE BMCreceiver does not enforce the PD object-count limit in hardware. Theexisting FIXME flagged this as unverified.Independently, regmap_read() takes an unsigned int * and stores a fullunsigned int at the destination. Passing the byte pointer msg + i meanseach iteration writes four bytes; the high three are zero (val_bits is8) and are normally overwritten by the next iteration, but the finaliteration's high bytes are not. With RXBYTES == 30 the i == 29 iterationalready writes three zero bytes past msg, which sits on the IRQ thread'sstack in wcove_typec_irq().Clamp the loop to sizeof(struct pd_message) and read each register intoa local before storing only its low byte, so the copy can never exceedthe destination regardless of what RXINFO reports.The Linux kernel CVE team has assigned CVE-2026-63960 to this issue.
已分析 2.openEulerScore 6.8
已分析 3.openEulerVector AV:P/AC:L/PR:N/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-botopeneuler-ci-botCollaborators
Jul 27 changed custom state from 进行中 to 已完成
openeuler-ci-botopeneuler-ci-botCollaborators
Jul 27 Close issue
openeuler-ci-botopeneuler-ci-botCollaborators
Jul 27 Removed label: CVE/UNFIXED
openeuler-ci-botopeneuler-ci-botCollaborators
Jul 27 Added label: CVE/FIXED
kunlunkunlunCollaborators
Aug 11 Associated pull request
hulk-ci-botCollaborators
19 days ago Comments:

openEuler评分:(评分和向量)
5.5
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

likedislike
hulk-ci-botCollaborators
18 days ago Comments:

openEuler评分:(评分和向量)
5.5
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

likedislike
hulk-ci-botCollaborators
17 days ago Comments:

openEuler评分:(评分和向量)
5.5
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

likedislike
hulk-ci-botCollaborators
16 days ago Comments:

openEuler评分:(评分和向量)
5.5
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

likedislike
hulk-ci-botCollaborators
15 days ago Comments:

openEuler评分:(评分和向量)
5.5
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

likedislike
hulk-ci-botCollaborators
14 days ago Comments:

openEuler评分:(评分和向量)
5.5
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

likedislike
hulk-ci-botCollaborators
13 days ago Comments:

openEuler评分:(评分和向量)
5.5
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

likedislike
hulk-ci-botCollaborators
12 days ago Comments:

openEuler评分:(评分和向量)
5.5
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

likedislike
hulk-ci-botCollaborators
11 days ago Comments:

openEuler评分:(评分和向量)
5.5
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

likedislike
openeuler-ci-bot
openeuler-ci-botCollaborators
7 days ago Comments:

source: @hulk-ci-bot

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

usb: typec: wcove: don't write past struct pd_message in wcove_read_rx_buffer()

wcove_read_rx_buffer() copies the PD RX FIFO into the caller's
struct pd_message with

for (i = 0; i &lt; USBC_RXINFO_RXBYTES(info); i++)
	regmap_read(wcove-&gt;regmap, USBC_RX_DATA + i, msg + i);

which has two problems:

USBC_RXINFO_RXBYTES() is a 5-bit field (max 31) while struct pd_message
is 30 bytes (__le16 header + __le32 payload[PD_MAX_PAYLOAD], packed).
The byte count latched in RXINFO is the number of bytes the port partner
put on the wire, so a malicious partner that transmits a 31-byte frame
can drive the loop one byte past the destination if the WCOVE BMC
receiver does not enforce the PD object-count limit in hardware. The
existing FIXME flagged this as unverified.

Independently, regmap_read() takes an unsigned int * and stores a full
unsigned int at the destination. Passing the byte pointer msg + i means
each iteration writes four bytes; the high three are zero (val_bits is
8) and are normally overwritten by the next iteration, but the final
iteration's high bytes are not. With RXBYTES == 30 the i == 29 iteration
already writes three zero bytes past msg, which sits on the IRQ thread's
stack in wcove_typec_irq().

Clamp the loop to sizeof(struct pd_message) and read each register into
a local before storing only its low byte, so the copy can never exceed
the destination regardless of what RXINFO reports.

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

openEuler评分:
5.5
AV:L/AC:L/PR:L/UI:N/S:U/C:N/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:应源码修复-openEuler社区发布软件包不受影响
5.openEuler-24.03-LTS:不修复-超出修复范围
6.openEuler-24.03-LTS-Next:不受影响-漏洞代码不能被攻击者触发
7.openEuler-24.03-LTS-SP1:应源码修复-openEuler社区发布软件包不受影响
8.openEuler-24.03-LTS-SP2:不修复-超出修复范围
9.openEuler-24.03-LTS-SP3:应源码修复-openEuler社区发布软件包不受影响
10.openEuler-24.03-LTS-SP4:应源码修复-openEuler社区发布软件包不受影响

likedislike
openeuler-ci-botopeneuler-ci-botCollaborators
7 days ago Added label: CVE/Need-Source-Fix
openeuler-ci-bot
openeuler-ci-botCollaborators
7 days ago Comments:

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

状态 分析项目 内容
已分析 1.影响性分析说明 In the Linux kernel, the following vulnerability has been resolved:usb: typec: wcove: don't write past struct pd_message in wcove_read_rx_buffer()wcove_read_rx_buffer() copies the PD RX FIFO into the caller'sstruct pd_message withfor (i = 0; i < USBC_RXINFO_RXBYTES(info); i++)regmap_read(wcove->regmap, USBC_RX_DATA + i, msg + i);which has two problems:USBC_RXINFO_RXBYTES() is a 5-bit field (max 31) while struct pd_messageis 30 bytes (__le16 header + __le32 payload[PD_MAX_PAYLOAD], packed).The byte count latched in RXINFO is the number of bytes the port partnerput on the wire, so a malicious partner that transmits a 31-byte framecan drive the loop one byte past the destination if the WCOVE BMCreceiver does not enforce the PD object-count limit in hardware. Theexisting FIXME flagged this as unverified.Independently, regmap_read() takes an unsigned int * and stores a fullunsigned int at the destination. Passing the byte pointer msg + i meanseach iteration writes four bytes; the high three are zero (val_bits is8) and are normally overwritten by the next iteration, but the finaliteration's high bytes are not. With RXBYTES == 30 the i == 29 iterationalready writes three zero bytes past msg, which sits on the IRQ thread'sstack in wcove_typec_irq().Clamp the loop to sizeof(struct pd_message) and read each register intoa local before storing only its low byte, so the copy can never exceedthe destination regardless of what RXINFO reports.The Linux kernel CVE team has assigned CVE-2026-63960 to this issue.
已分析 2.openEulerScore 5.5
已分析 3.openEulerVector AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
已分析 4.受影响版本排查 master:不受影响,openEuler-20.03-LTS-SP4:受影响,openEuler-22.03-LTS-SP3:受影响,openEuler-22.03-LTS-SP4:受影响,openEuler-24.03-LTS:受影响,openEuler-24.03-LTS-Next:不受影响,openEuler-24.03-LTS-SP1:受影响,openEuler-24.03-LTS-SP2:受影响,openEuler-24.03-LTS-SP3:受影响,openEuler-24.03-LTS-SP4:受影响
已分析 5.是否涉及abi变化 master:否,openEuler-20.03-LTS-SP4:否,openEuler-22.03-LTS-SP3:否,openEuler-22.03-LTS-SP4:否,openEuler-24.03-LTS:否,openEuler-24.03-LTS-Next:否,openEuler-24.03-LTS-SP1:否,openEuler-24.03-LTS-SP2:否,openEuler-24.03-LTS-SP3:否,openEuler-24.03-LTS-SP4:否
已分析 6.原因说明 master:不受影响-漏洞代码不能被攻击者触发,openEuler-20.03-LTS-SP4:暂不修复-漏洞仍在分析中,openEuler-22.03-LTS-SP3:不修复-超出修复范围,openEuler-22.03-LTS-SP4:应源码修复-openEuler社区发布软件包不受影响,openEuler-24.03-LTS:不修复-超出修复范围,openEuler-24.03-LTS-Next:不受影响-漏洞代码不能被攻击者触发,openEuler-24.03-LTS-SP1:应源码修复-openEuler社区发布软件包不受影响,openEuler-24.03-LTS-SP2:不修复-超出修复范围,openEuler-24.03-LTS-SP3:应源码修复-openEuler社区发布软件包不受影响,openEuler-24.03-LTS-SP4:应源码修复-openEuler社区发布软件包不受影响

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

likedislike
openeuler-ci-bot
openeuler-ci-botCollaborators
7 days ago Comments:

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

原因说明:
1.master:不受影响-漏洞代码不能被攻击者触发
2.openEuler-20.03-LTS-SP4:暂不修复-漏洞仍在分析中
3.openEuler-22.03-LTS-SP3:不修复-超出修复范围
4.openEuler-22.03-LTS-SP4:应源码修复-openEuler社区发布软件包不受影响
5.openEuler-24.03-LTS:不修复-超出修复范围
6.openEuler-24.03-LTS-Next:不受影响-漏洞代码不能被攻击者触发
7.openEuler-24.03-LTS-SP1:应源码修复-openEuler社区发布软件包不受影响(PR未合入)
8.openEuler-24.03-LTS-SP2:不修复-超出修复范围
9.openEuler-24.03-LTS-SP3:应源码修复-openEuler社区发布软件包不受影响(PR未合入)
10.openEuler-24.03-LTS-SP4:应源码修复-openEuler社区发布软件包不受影响(PR未合入)

likedislike
openeuler-ci-botopeneuler-ci-botCollaborators
7 days ago changed custom state from 已完成 to 进行中
8 event messages are collapsed here。 See more
openeuler-ci-botopeneuler-ci-botCollaborators
11 hours ago Modify description of issue