CVE-2024-36893

一、漏洞信息
漏洞编号：CVE-2024-36893
漏洞归属组件：kernel
漏洞归属的版本：4.19.140,4.19.194,4.19.90,5.10.0,6.1.0,6.1.14,6.1.19,6.1.5,6.1.6,6.1.8,6.4.0,6.6.0
CVSS V3.0分值：
BaseScore：5.5 Medium
Vector：CVSS：3.0/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: tcpm: Check for port partner validity before consuming ittypec_register_partner() does not guarantee partner registrationto always succeed. In the event of failure, port->partner is setto the error value or NULL. Given that port->partner validity isnot checked, this results in the following crash:Unable to handle kernel NULL pointer dereference at virtual address xx pc : run_state_machine+0x1bc8/0x1c08 lr : run_state_machine+0x1b90/0x1c08.. Call trace: run_state_machine+0x1bc8/0x1c08 tcpm_state_machine_work+0x94/0xe4 kthread_worker_fn+0x118/0x328 kthread+0x1d0/0x23c ret_from_fork+0x10/0x20To prevent the crash, check for port->partner validity beforederefencing it in all the call sites.
漏洞公开时间：2024-05-31 00:15:12
漏洞创建时间：2024-06-02 05:47:37
漏洞详情参考链接：
https://nvd.nist.gov/vuln/detail/CVE-2024-36893

更多参考(点击展开)

参考来源	参考链接	来源链接
416baaa9-dc9f-4396-8d5f-8c081fb06d67	https://git.kernel.org/stable/c/789326cafbd1f67f424436b6bc8bdb887a364637
416baaa9-dc9f-4396-8d5f-8c081fb06d67	https://git.kernel.org/stable/c/ae11f04b452b5205536e1c02d31f8045eba249dd
416baaa9-dc9f-4396-8d5f-8c081fb06d67	https://git.kernel.org/stable/c/d56d2ca03cc22123fd7626967d096d8661324e57
416baaa9-dc9f-4396-8d5f-8c081fb06d67	https://git.kernel.org/stable/c/fc2b655cb6dd2b381f1f284989721002e39b6b77
suse_bugzilla	http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-36893	https://bugzilla.suse.com/show_bug.cgi?id=1225748
suse_bugzilla	https://git.kernel.org/pub/scm/linux/security/vulns.git/plain/cve/published/2024/CVE-2024-36893.mbox	https://bugzilla.suse.com/show_bug.cgi?id=1225748
suse_bugzilla	https://git.kernel.org/stable/c/d56d2ca03cc22123fd7626967d096d8661324e57	https://bugzilla.suse.com/show_bug.cgi?id=1225748
suse_bugzilla	https://git.kernel.org/stable/c/789326cafbd1f67f424436b6bc8bdb887a364637	https://bugzilla.suse.com/show_bug.cgi?id=1225748
suse_bugzilla	https://git.kernel.org/stable/c/fc2b655cb6dd2b381f1f284989721002e39b6b77	https://bugzilla.suse.com/show_bug.cgi?id=1225748
suse_bugzilla	https://git.kernel.org/stable/c/ae11f04b452b5205536e1c02d31f8045eba249dd	https://bugzilla.suse.com/show_bug.cgi?id=1225748
suse_bugzilla	https://www.cve.org/CVERecord?id=CVE-2024-36893	https://bugzilla.suse.com/show_bug.cgi?id=1225748
redhat_bugzilla	https://lore.kernel.org/linux-cve-announce/2024053034-CVE-2024-36893-476e@gregkh/T	https://bugzilla.redhat.com/show_bug.cgi?id=2284563
ubuntu	https://www.cve.org/CVERecord?id=CVE-2024-36893	https://ubuntu.com/security/CVE-2024-36893
ubuntu	https://git.kernel.org/linus/ae11f04b452b5205536e1c02d31f8045eba249dd (6.9-rc7)	https://ubuntu.com/security/CVE-2024-36893
ubuntu	https://git.kernel.org/stable/c/d56d2ca03cc22123fd7626967d096d8661324e57	https://ubuntu.com/security/CVE-2024-36893
ubuntu	https://git.kernel.org/stable/c/789326cafbd1f67f424436b6bc8bdb887a364637	https://ubuntu.com/security/CVE-2024-36893
ubuntu	https://git.kernel.org/stable/c/fc2b655cb6dd2b381f1f284989721002e39b6b77	https://ubuntu.com/security/CVE-2024-36893
ubuntu	https://git.kernel.org/stable/c/ae11f04b452b5205536e1c02d31f8045eba249dd	https://ubuntu.com/security/CVE-2024-36893
ubuntu	https://nvd.nist.gov/vuln/detail/CVE-2024-36893	https://ubuntu.com/security/CVE-2024-36893
ubuntu	https://launchpad.net/bugs/cve/CVE-2024-36893	https://ubuntu.com/security/CVE-2024-36893
ubuntu	https://security-tracker.debian.org/tracker/CVE-2024-36893	https://ubuntu.com/security/CVE-2024-36893
debian		https://security-tracker.debian.org/tracker/CVE-2024-36893
416baaa9-dc9f-4396-8d5f-8c081fb06d67	https://git.kernel.org/stable/c/789326cafbd1f67f424436b6bc8bdb887a364637
416baaa9-dc9f-4396-8d5f-8c081fb06d67	https://git.kernel.org/stable/c/ae11f04b452b5205536e1c02d31f8045eba249dd
416baaa9-dc9f-4396-8d5f-8c081fb06d67	https://git.kernel.org/stable/c/d56d2ca03cc22123fd7626967d096d8661324e57
416baaa9-dc9f-4396-8d5f-8c081fb06d67	https://git.kernel.org/stable/c/fc2b655cb6dd2b381f1f284989721002e39b6b77

漏洞分析指导链接：
https://gitee.com/openeuler/cve-manager/blob/master/cve-vulner-manager/doc/md/manual.md
漏洞数据来源:
openBrain开源漏洞感知系统
漏洞补丁信息：

详情(点击展开)

影响的包	修复补丁	问题引入补丁	来源
	https://git.kernel.org/stable/c/789326cafbd1f67f424436b6bc8bdb887a364637		nvd
	https://git.kernel.org/stable/c/ae11f04b452b5205536e1c02d31f8045eba249dd		nvd
	https://git.kernel.org/stable/c/d56d2ca03cc22123fd7626967d096d8661324e57		nvd
	https://git.kernel.org/stable/c/fc2b655cb6dd2b381f1f284989721002e39b6b77		nvd
linux	https://git.kernel.org/linus/ae11f04b452b5205536e1c02d31f8045eba249dd	https://git.kernel.org/linus/c97cd0b4b54eb42aed7f6c3c295a2d137f6d2416	ubuntu

二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:usb: typec: tcpm: Check for port partner validity before consuming ittypec_register_partner() does not guarantee partner registrationto always succeed. In the event of failure, port->partner is setto the error value or NULL. Given that port->partner validity isnot checked, this results in the following crash:Unable to handle kernel NULL pointer dereference at virtual address xx pc : run_state_machine+0x1bc8/0x1c08 lr : run_state_machine+0x1b90/0x1c08.. Call trace: run_state_machine+0x1bc8/0x1c08 tcpm_state_machine_work+0x94/0xe4 kthread_worker_fn+0x118/0x328 kthread+0x1d0/0x23c ret_from_fork+0x10/0x20To prevent the crash, check for port->partner validity beforederefencing it in all the call sites.
openEuler评分：
5.5
Vector：CVSS：3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
受影响版本排查(受影响/不受影响)：
1.openEuler-24.03-LTS(6.6.0):不受影响
2.openEuler-20.03-LTS-SP4(4.19.90):不受影响
3.openEuler-22.03-LTS-SP1(5.10.0):不受影响
4.openEuler-22.03-LTS-SP3(5.10.0):不受影响
5.openEuler-22.03-LTS-SP4(5.10.0):不受影响
6.master(6.1.0):不受影响
7.openEuler-24.03-LTS-Next(6.6.0):不受影响

修复是否涉及abi变化(是/否)：
1.openEuler-20.03-LTS-SP4(4.19.90):否
2.openEuler-22.03-LTS-SP1(5.10.0):否
3.openEuler-22.03-LTS-SP3(5.10.0):否
4.master(6.1.0):否
5.openEuler-24.03-LTS(6.6.0):否
6.openEuler-24.03-LTS-Next(6.6.0):否
7.openEuler-22.03-LTS-SP4(5.10.0):否

@yangyingliang ,@jiaoff ,@guohaocs2c ,@hanjun-guo ,@woqidaideshi ,@newbeats ,@zhangyi089 ,@colyli ,@thundertown ,@htforge ,@chiqijun ,@lengchao ,@zhujianwei001 ,@kylin-mayukun ,@wangxiongfeng ,@wkfxxx ,@SuperSix173 ,@jentlestea ,@oskernel0719 ,@gasonchen 
**issue处理注意事项:** 
**1. 当前issue受影响的分支提交pr时, 须在pr描述中填写当前issue编号进行关联, 否则无法关闭当前issue;**
**2. 模板内容需要填写完整, 无论是受影响或者不受影响都需要填写完整内容,未引入的分支不需要填写, 否则无法关闭当前issue;**
**3. 以下为模板中需要填写完整的内容, 请复制到评论区回复, 注: 内容的标题名称(影响性分析说明, openEuler评分, 受影响版本排查(受影响/不受影响), 修复是否涉及abi变化(是/否))不能省略,省略后cve-manager将无法正常解析填写内容.**
************************************************************************
影响性分析说明:

openEuler评分: (评分和向量)

受影响版本排查(受影响/不受影响): 
1.master(6.1.0):
2.openEuler-20.03-LTS-SP1(4.19.90):
3.openEuler-20.03-LTS-SP4(4.19.90):
4.openEuler-22.03-LTS(5.10.0):
5.openEuler-22.03-LTS-Next(5.10.0):
6.openEuler-22.03-LTS-SP1(5.10.0):
7.openEuler-22.03-LTS-SP2(5.10.0):
8.openEuler-22.03-LTS-SP3(5.10.0):
9.openEuler-22.03-LTS-SP4(5.10.0):
10.openEuler-24.03-LTS(6.6.0):
11.openEuler-24.03-LTS-Next(6.6.0):

修复是否涉及abi变化(是/否)：
1.master(6.1.0):
2.openEuler-20.03-LTS-SP1(4.19.90):
3.openEuler-20.03-LTS-SP4(4.19.90):
4.openEuler-22.03-LTS(5.10.0):
5.openEuler-22.03-LTS-Next(5.10.0):
6.openEuler-22.03-LTS-SP1(5.10.0):
7.openEuler-22.03-LTS-SP2(5.10.0):
8.openEuler-22.03-LTS-SP3(5.10.0):
9.openEuler-22.03-LTS-SP4(5.10.0):
10.openEuler-24.03-LTS(6.6.0):
11.openEuler-24.03-LTS-Next(6.6.0):

-----------------------------------------------------------------------
issue处理具体操作请参考: 
https://gitee.com/openeuler/cve-manager/blob/master/cve-vulner-manager/doc/md/manual.md
pr关联issue具体操作请参考:
https://gitee.com/help/articles/4142

Hi openeuler-ci-bot, welcome to the openEuler Community.
I'm the Bot here serving you. You can find the instructions on how to interact with me at Here.
If you have any questions, please contact the SIG: Kernel, and any of the maintainers.

参考网址	关联pr	状态	补丁链接
https://nvd.nist.gov/vuln/detail/CVE-2024-36893	None	None	https://git.kernel.org/stable/c/ae11f04b452b5205536e1c02d31f8045eba249dd https://git.kernel.org/stable/c/789326cafbd1f67f424436b6bc8bdb887a364637 https://git.kernel.org/stable/c/d56d2ca03cc22123fd7626967d096d8661324e57 https://git.kernel.org/stable/c/fc2b655cb6dd2b381f1f284989721002e39b6b77
https://ubuntu.com/security/CVE-2024-36893	None	None	https://git.kernel.org/stable/c/fc2b655cb6dd2b381f1f284989721002e39b6b77 https://git.kernel.org/linus/c97cd0b4b54eb42aed7f6c3c295a2d137f6d2416 https://discourse.ubuntu.com/c/ubuntu-pro https://git.kernel.org/stable/c/ae11f04b452b5205536e1c02d31f8045eba249dd https://git.kernel.org/stable/c/789326cafbd1f67f424436b6bc8bdb887a364637 https://git.kernel.org/stable/c/d56d2ca03cc22123fd7626967d096d8661324e57 https://git.kernel.org/linus/ae11f04b452b5205536e1c02d31f8045eba249dd
https://www.opencve.io/cve/CVE-2024-36893	None	None	https://git.kernel.org/stable/c/ae11f04b452b5205536e1c02d31f8045eba249dd https://git.kernel.org/stable/c/789326cafbd1f67f424436b6bc8bdb887a364637 https://git.kernel.org/stable/c/d56d2ca03cc22123fd7626967d096d8661324e57 https://git.kernel.org/stable/c/fc2b655cb6dd2b381f1f284989721002e39b6b77
https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2024-36893
https://security-tracker.debian.org/tracker/CVE-2024-36893	None	None	https://git.kernel.org/linus/ae11f04b452b5205536e1c02d31f8045eba249dd

说明：补丁链接仅供初步排查参考，实际可用性请人工再次确认，补丁下载验证可使用CVE补丁工具。
若补丁不准确，烦请在此issue下评论 '/report-patch 参考网址补丁链接1,补丁链接2' 反馈正确信息，便于我们不断优化工具，不胜感激。
如 /report-patch https://security-tracker.debian.org/tracker/CVE-2021-3997 https://github.com/systemd/systemd/commit/5b1cf7a9be37e20133c0208005274ce4a5b5c6a1

CVE-2024-36893

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

usb: typec: tcpm: Check for port partner validity before consuming it

typec_register_partner() does not guarantee partner registration
to always succeed. In the event of failure, port->partner is set
to the error value or NULL. Given that port->partner validity is
not checked, this results in the following crash:

Unable to handle kernel NULL pointer dereference at virtual address xx
pc : run_state_machine+0x1bc8/0x1c08
lr : run_state_machine+0x1b90/0x1c08
..
Call trace:
run_state_machine+0x1bc8/0x1c08
tcpm_state_machine_work+0x94/0xe4
kthread_worker_fn+0x118/0x328
kthread+0x1d0/0x23c
ret_from_fork+0x10/0x20

To prevent the crash, check for port->partner validity before
derefencing it in all the call sites.

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

受影响版本排查(受影响/不受影响):
1.openEuler-20.03-LTS-SP4:不受影响
2.openEuler-22.03-LTS-SP1:不受影响
3.openEuler-22.03-LTS-SP3:不受影响
4.openEuler-22.03-LTS-SP4:不受影响
5.master(6.1.0):不受影响
6.openEuler-24.03-LTS:受影响
7.openEuler-24.03-LTS-Next:不受影响

修复是否涉及abi变化(是/否)：
1.openEuler-20.03-LTS-SP4:否
2.openEuler-22.03-LTS-SP1:否
3.openEuler-22.03-LTS-SP3:否
4.master(6.1.0):否
5.openEuler-24.03-LTS:否
6.openEuler-24.03-LTS-Next:否
7.openEuler-22.03-LTS-SP4:否

===========================================================

@sanglipeng 经过 cve-manager 解析, 已分析的内容如下表所示:
| 状态  | 需分析 | 内容 |
|:--:|:--:|---------|
|已分析|1.影响性分析说明|In the Linux kernel, the following vulnerability has been resolved:usb: typec: tcpm: Check for port partner validity before consuming ittypec_register_partner() does not guarantee partner registrationto always succeed. In the event of failure, port->partner is setto the error value or NULL. Given that port->partner validity isnot checked, this results in the following crash:Unable to handle kernel NULL pointer dereference at virtual address xx pc : run_state_machine+0x1bc8/0x1c08 lr : run_state_machine+0x1b90/0x1c08.. Call trace:   run_state_machine+0x1bc8/0x1c08   tcpm_state_machine_work+0x94/0xe4   kthread_worker_fn+0x118/0x328   kthread+0x1d0/0x23c   ret_from_fork+0x10/0x20To prevent the crash, check for port->partner validity beforederefencing it in all the call sites.|
|已分析|2.openEulerScore|5.5|
|已分析|3.openEulerVector|AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H|
|已分析|4.受影响版本排查|openEuler-24.03-LTS:受影响,openEuler-20.03-LTS-SP4:不受影响,openEuler-22.03-LTS-SP1:不受影响,openEuler-22.03-LTS-SP3:不受影响,openEuler-22.03-LTS-SP4:不受影响,master:不受影响,openEuler-24.03-LTS-Next:不受影响|
|已分析|5.修复是否涉及abi变化|openEuler-20.03-LTS-SP4:否,openEuler-22.03-LTS-SP1:否,openEuler-22.03-LTS-SP3:否,master:否,openEuler-24.03-LTS:否,openEuler-24.03-LTS-Next:否,openEuler-22.03-LTS-SP4:否|

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

受影响版本排查(受影响/不受影响)：
1.openEuler-24.03-LTS(6.6.0):不受影响
2.openEuler-20.03-LTS-SP4(4.19.90):不受影响
3.openEuler-22.03-LTS-SP1(5.10.0):不受影响
4.openEuler-22.03-LTS-SP3(5.10.0):不受影响
5.openEuler-22.03-LTS-SP4(5.10.0):不受影响
6.master(6.1.0):不受影响
7.openEuler-24.03-LTS-Next(6.6.0):不受影响

@sanglipeng 经过 cve-manager 解析, 已分析的内容如下表所示:
| 状态  | 需分析 | 内容 |
|:--:|:--:|---------|
|已分析|1.影响性分析说明|  In the Linux kernel, the following vulnerability has been resolved:usb: typec: tcpm: Check for port partner validity before consuming ittypec_register_partner() does not guarantee partner registrationto always succeed. In the event of failure, port->partner is setto the error value or NULL. Given that port->partner validity isnot checked, this results in the following crash:Unable to handle kernel NULL pointer dereference at virtual address xx pc : run_state_machine+0x1bc8/0x1c08 lr : run_state_machine+0x1b90/0x1c08.. Call trace:   run_state_machine+0x1bc8/0x1c08   tcpm_state_machine_work+0x94/0xe4   kthread_worker_fn+0x118/0x328   kthread+0x1d0/0x23c   ret_from_fork+0x10/0x20To prevent the crash, check for port->partner validity beforederefencing it in all the call sites. |
|已分析|2.openEulerScore|5.5|
|已分析|3.openEulerVector|AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H|
|已分析|4.受影响版本排查|openEuler-24.03-LTS:不受影响,openEuler-20.03-LTS-SP4:不受影响,openEuler-22.03-LTS-SP1:不受影响,openEuler-22.03-LTS-SP3:不受影响,openEuler-22.03-LTS-SP4:不受影响,master:不受影响,openEuler-24.03-LTS-Next:不受影响|
|已分析|5.修复是否涉及abi变化|openEuler-20.03-LTS-SP4:否,openEuler-22.03-LTS-SP1:否,openEuler-22.03-LTS-SP3:否,master:否,openEuler-24.03-LTS:否,openEuler-24.03-LTS-Next:否,openEuler-22.03-LTS-SP4:否|

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

CVE-2024-36893

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

usb: typec: tcpm: Check for port partner validity before consuming it

typec_register_partner() does not guarantee partner registration
to always succeed. In the event of failure, port->partner is set
to the error value or NULL. Given that port->partner validity is
not checked, this results in the following crash:

Unable to handle kernel NULL pointer dereference at virtual address xx
pc : run_state_machine+0x1bc8/0x1c08
lr : run_state_machine+0x1b90/0x1c08
..
Call trace:
run_state_machine+0x1bc8/0x1c08
tcpm_state_machine_work+0x94/0xe4
kthread_worker_fn+0x118/0x328
kthread+0x1d0/0x23c
ret_from_fork+0x10/0x20

To prevent the crash, check for port->partner validity before
derefencing it in all the call sites.

The Linux kernel CVE team has assigned CVE-2024-36893 to this issue.