CVE-2024-56691

一、漏洞信息
漏洞编号：CVE-2024-56691
漏洞归属组件：kernel
漏洞归属的版本：4.19.140,4.19.194,4.19.90,5.10.0,6.1.19,6.1.8,6.4.0,6.6.0
CVSS V3.0分值：
BaseScore：N/A None
Vector：CVSS：3.0/
漏洞简述：
In the Linux kernel, the following vulnerability has been resolved:mfd: intel_soc_pmic_bxtwc: Use IRQ domain for USB Type-C deviceWhile design wise the idea of converting the driver to usethe hierarchy of the IRQ chips is correct, the implementationhas (inherited) flaws. This was unveiled when platform_get_irq()had started WARN() on IRQ 0 that is supposed to be a LinuxIRQ number (also known as vIRQ).Rework the driver to respect IRQ domain when creating each MFDdevice separately, as the domain is not the same for all of them.
漏洞公开时间：2024-12-28 18:15:14
漏洞创建时间：2024-12-28 18:30:57
漏洞详情参考链接：
https://nvd.nist.gov/vuln/detail/CVE-2024-56691

更多参考(点击展开)

参考来源	参考链接	来源链接
416baaa9-dc9f-4396-8d5f-8c081fb06d67	https://git.kernel.org/stable/c/0997e77c51330c2866a4f39480e762cca92ad953
416baaa9-dc9f-4396-8d5f-8c081fb06d67	https://git.kernel.org/stable/c/0b648968bfa4f5c9c4983bca9f2de17626ed6fb6
416baaa9-dc9f-4396-8d5f-8c081fb06d67	https://git.kernel.org/stable/c/23230ac3c5ca3f154b64849d1cf50583b4e6b98c
416baaa9-dc9f-4396-8d5f-8c081fb06d67	https://git.kernel.org/stable/c/518e414d24e7037d6cc7198e942bf47fe6f5e8e1
416baaa9-dc9f-4396-8d5f-8c081fb06d67	https://git.kernel.org/stable/c/686fb77712a4bc94b76a0c5ae74c60118b7a0d79
416baaa9-dc9f-4396-8d5f-8c081fb06d67	https://git.kernel.org/stable/c/87a07a5b0b296e489c606ca95ffc16c18821975b
416baaa9-dc9f-4396-8d5f-8c081fb06d67	https://git.kernel.org/stable/c/c310e6916c0b297011d0fec03f168a6b24e9e984
416baaa9-dc9f-4396-8d5f-8c081fb06d67	https://git.kernel.org/stable/c/e1ef62e8d262e3f27446d26742208c1c81e9ee18
suse_bugzilla	http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-56691	https://bugzilla.suse.com/show_bug.cgi?id=1235425
suse_bugzilla	https://git.kernel.org/pub/scm/linux/security/vulns.git/plain/cve/published/2024/CVE-2024-56691.mbox	https://bugzilla.suse.com/show_bug.cgi?id=1235425
suse_bugzilla	https://git.kernel.org/stable/c/0997e77c51330c2866a4f39480e762cca92ad953	https://bugzilla.suse.com/show_bug.cgi?id=1235425
suse_bugzilla	https://git.kernel.org/stable/c/0b648968bfa4f5c9c4983bca9f2de17626ed6fb6	https://bugzilla.suse.com/show_bug.cgi?id=1235425
suse_bugzilla	https://git.kernel.org/stable/c/23230ac3c5ca3f154b64849d1cf50583b4e6b98c	https://bugzilla.suse.com/show_bug.cgi?id=1235425
suse_bugzilla	https://git.kernel.org/stable/c/c310e6916c0b297011d0fec03f168a6b24e9e984	https://bugzilla.suse.com/show_bug.cgi?id=1235425
suse_bugzilla	https://git.kernel.org/stable/c/e1ef62e8d262e3f27446d26742208c1c81e9ee18	https://bugzilla.suse.com/show_bug.cgi?id=1235425
suse_bugzilla	https://git.kernel.org/stable/c/518e414d24e7037d6cc7198e942bf47fe6f5e8e1	https://bugzilla.suse.com/show_bug.cgi?id=1235425
suse_bugzilla	https://git.kernel.org/stable/c/87a07a5b0b296e489c606ca95ffc16c18821975b	https://bugzilla.suse.com/show_bug.cgi?id=1235425
suse_bugzilla	https://git.kernel.org/stable/c/686fb77712a4bc94b76a0c5ae74c60118b7a0d79	https://bugzilla.suse.com/show_bug.cgi?id=1235425
suse_bugzilla	https://www.cve.org/CVERecord?id=CVE-2024-56691	https://bugzilla.suse.com/show_bug.cgi?id=1235425
suse_bugzilla	https://bugzilla.redhat.com/show_bug.cgi?id=2334684	https://bugzilla.suse.com/show_bug.cgi?id=1235425
redhat_bugzilla	https://lore.kernel.org/linux-cve-announce/2024122834-CVE-2024-56691-c981@gregkh/T	https://bugzilla.redhat.com/show_bug.cgi?id=2334684
debian		https://security-tracker.debian.org/tracker/CVE-2024-56691
osv	https://git.kernel.org/stable/c/0997e77c51330c2866a4f39480e762cca92ad953	https://osv.dev/vulnerability/CVE-2024-56691
osv	https://git.kernel.org/stable/c/0b648968bfa4f5c9c4983bca9f2de17626ed6fb6	https://osv.dev/vulnerability/CVE-2024-56691
osv	https://git.kernel.org/stable/c/23230ac3c5ca3f154b64849d1cf50583b4e6b98c	https://osv.dev/vulnerability/CVE-2024-56691
osv	https://git.kernel.org/stable/c/518e414d24e7037d6cc7198e942bf47fe6f5e8e1	https://osv.dev/vulnerability/CVE-2024-56691
osv	https://git.kernel.org/stable/c/686fb77712a4bc94b76a0c5ae74c60118b7a0d79	https://osv.dev/vulnerability/CVE-2024-56691
osv	https://git.kernel.org/stable/c/87a07a5b0b296e489c606ca95ffc16c18821975b	https://osv.dev/vulnerability/CVE-2024-56691
osv	https://git.kernel.org/stable/c/c310e6916c0b297011d0fec03f168a6b24e9e984	https://osv.dev/vulnerability/CVE-2024-56691
osv	https://git.kernel.org/stable/c/e1ef62e8d262e3f27446d26742208c1c81e9ee18	https://osv.dev/vulnerability/CVE-2024-56691
osv	https://security-tracker.debian.org/tracker/CVE-2024-56691	https://osv.dev/vulnerability/CVE-2024-56691

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

详情(点击展开)

影响的包	修复版本	修复补丁	问题引入补丁	来源
linux_kernel	5.4.287	https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=0997e77c51330c2866a4f39480e762cca92ad953Issue	https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=9c6235c8633210cc2da0882e2e9d6ff90aa37503	linuxkernelcves
linux_kernel	5.10.231	https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=0b648968bfa4f5c9c4983bca9f2de17626ed6fb6Issue	https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=9c6235c8633210cc2da0882e2e9d6ff90aa37503	linuxkernelcves
linux_kernel	5.15.174	https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=23230ac3c5ca3f154b64849d1cf50583b4e6b98cIssue	https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=9c6235c8633210cc2da0882e2e9d6ff90aa37503	linuxkernelcves
linux_kernel	6.1.120	https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=c310e6916c0b297011d0fec03f168a6b24e9e984Issue	https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=9c6235c8633210cc2da0882e2e9d6ff90aa37503	linuxkernelcves
linux_kernel	6.6.64	https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=e1ef62e8d262e3f27446d26742208c1c81e9ee18Issue	https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=9c6235c8633210cc2da0882e2e9d6ff90aa37503	linuxkernelcves
linux_kernel	6.11.11	https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=518e414d24e7037d6cc7198e942bf47fe6f5e8e1Issue	https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=9c6235c8633210cc2da0882e2e9d6ff90aa37503	linuxkernelcves
linux_kernel	6.12.2	https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=87a07a5b0b296e489c606ca95ffc16c18821975bIssue	https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=9c6235c8633210cc2da0882e2e9d6ff90aa37503	linuxkernelcves
linux_kernel	6.13-rc1	https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=686fb77712a4bc94b76a0c5ae74c60118b7a0d79Please	https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=9c6235c8633210cc2da0882e2e9d6ff90aa37503	linuxkernelcves

二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:mfd: intel_soc_pmic_bxtwc: Use IRQ domain for USB Type-C deviceWhile design wise the idea of converting the driver to usethe hierarchy of the IRQ chips is correct, the implementationhas (inherited) flaws. This was unveiled when platform_get_irq()had started WARN() on IRQ 0 that is supposed to be a LinuxIRQ number (also known as vIRQ).Rework the driver to respect IRQ domain when creating each MFDdevice separately, as the domain is not the same for all of them.The Linux kernel CVE team has assigned CVE-2024-56691 to this issue.
openEuler评分：
3.9
Vector：CVSS：3.0/AV:L/AC:H/PR:H/UI:N/S:U/C:L/I:L/A:L
受影响版本排查(受影响/不受影响)：
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.openEuler-22.03-LTS-SP4(5.10.0):受影响
5.openEuler-24.03-LTS(6.6.0):受影响
6.openEuler-24.03-LTS-SP1(6.6.0):受影响
7.master(6.6.0):不受影响
8.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.6.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):否
8.openEuler-24.03-LTS-SP1(6.6.0):否

原因说明：
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.openEuler-22.03-LTS-SP4(5.10.0):正常修复
5.openEuler-24.03-LTS(6.6.0):正常修复
6.openEuler-24.03-LTS-SP1(6.6.0):正常修复
7.master(6.6.0):不受影响-漏洞代码不能被攻击者触发
8.openEuler-24.03-LTS-Next(6.6.0):不受影响-漏洞代码不能被攻击者触发

三、漏洞修复
安全公告链接：https://www.openeuler.org/zh/security/safety-bulletin/detail/?id=openEuler-SA-2025-1079

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.

@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.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.openEuler-24.03-LTS(6.6.0):
7.openEuler-24.03-LTS-Next(6.6.0):
8.openEuler-24.03-LTS-SP1(6.6.0):

修复是否涉及abi变化(是/否)：
1.master(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.openEuler-24.03-LTS(6.6.0):
7.openEuler-24.03-LTS-Next(6.6.0):
8.openEuler-24.03-LTS-SP1(6.6.0):

原因说明：
1.master(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.openEuler-24.03-LTS(6.6.0):
7.openEuler-24.03-LTS-Next(6.6.0):
8.openEuler-24.03-LTS-SP1(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

CVE-2024-56691

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

mfd: intel_soc_pmic_bxtwc: Use IRQ domain for USB Type-C device

While design wise the idea of converting the driver to use
the hierarchy of the IRQ chips is correct, the implementation
has (inherited) flaws. This was unveiled when platform_get_irq()
had started WARN() on IRQ 0 that is supposed to be a Linux
IRQ number (also known as vIRQ).

Rework the driver to respect IRQ domain when creating each MFD
device separately, as the domain is not the same for all of them.

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

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

受影响版本排查(受影响/不受影响):
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:不受影响
8.openEuler-24.03-LTS-SP1:受影响

修复是否涉及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:否
8.openEuler-24.03-LTS-SP1:否

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

@sanglipeng 经过 cve-manager 解析, 已分析的内容如下表所示:
| 状态  | 分析项目 | 内容 |
|:--:|:--:|---------|
|已分析|1.影响性分析说明|In the Linux kernel, the following vulnerability has been resolved:mfd: intel_soc_pmic_bxtwc: Use IRQ domain for USB Type-C deviceWhile design wise the idea of converting the driver to usethe hierarchy of the IRQ chips is correct, the implementationhas (inherited) flaws. This was unveiled when platform_get_irq()had started WARN() on IRQ 0 that is supposed to be a LinuxIRQ number (also known as vIRQ).Rework the driver to respect IRQ domain when creating each MFDdevice separately, as the domain is not the same for all of them.The Linux kernel CVE team has assigned CVE-2024-56691 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.受影响版本排查|openEuler-20.03-LTS-SP4:受影响,openEuler-22.03-LTS-SP1:受影响,openEuler-22.03-LTS-SP3:受影响,openEuler-22.03-LTS-SP4:受影响,openEuler-24.03-LTS:受影响,openEuler-24.03-LTS-SP1:受影响,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:否,openEuler-24.03-LTS-SP1:否|
|已分析|6.原因说明|openEuler-20.03-LTS-SP4:正常修复,openEuler-22.03-LTS-SP1:正常修复,openEuler-22.03-LTS-SP3:正常修复,openEuler-22.03-LTS-SP4:正常修复,openEuler-24.03-LTS:正常修复,openEuler-24.03-LTS-SP1:正常修复,master:不受影响-漏洞代码不能被攻击者触发,openEuler-24.03-LTS-Next:不受影响-漏洞代码不能被攻击者触发|

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

CVE-2024-56691

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

mfd: intel_soc_pmic_bxtwc: Use IRQ domain for USB Type-C device

While design wise the idea of converting the driver to use
the hierarchy of the IRQ chips is correct, the implementation
has (inherited) flaws. This was unveiled when platform_get_irq()
had started WARN() on IRQ 0 that is supposed to be a Linux
IRQ number (also known as vIRQ).

Rework the driver to respect IRQ domain when creating each MFD
device separately, as the domain is not the same for all of them.

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

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

受影响版本排查(受影响/不受影响):
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:不受影响
8.openEuler-24.03-LTS-SP1:受影响

修复是否涉及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:否
8.openEuler-24.03-LTS-SP1:否

原因说明：
1.master(23.08.5):不受影响-漏洞代码不能被攻击者触发
2.openEuler-20.03-LTS-SP4:暂不修复-暂无解决方案或补丁
3.openEuler-22.03-LTS-SP1:正常修复
4.openEuler-22.03-LTS-SP3:正常修复
5.openEuler-22.03-LTS-SP4:正常修复
6.openEuler-24.03-LTS:正常修复
7.openEuler-24.03-LTS-Next:不受影响-漏洞代码不能被攻击者触发
8.openEuler-24.03-LTS-SP1:正常修复