CVE-2024-47712

一、漏洞信息
漏洞编号：CVE-2024-47712
漏洞归属组件：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:wifi: wilc1000: fix potential RCU dereference issue in wilc_parse_join_bss_paramIn the wilc_parse_join_bss_param function, the TSF field of the iesstructure is accessed after the RCU read-side critical section isunlocked. According to RCU usage rules, this is illegal. Reusing thispointer can lead to unpredictable behavior, including accessing memorythat has been updated or causing use-after-free issues.This possible bug was identified using a static analysis tool developedby myself, specifically designed to detect RCU-related issues.To address this, the TSF value is now stored in a local variableies_tsf before the RCU lock is released. The param->tsf_lo field isthen assigned using this local variable, ensuring that the TSF value issafely accessed.
漏洞公开时间：2024-10-21 20:15:07
漏洞创建时间：2024-10-21 20:43:06
漏洞详情参考链接：
https://nvd.nist.gov/vuln/detail/CVE-2024-47712

更多参考(点击展开)

参考来源	参考链接	来源链接
416baaa9-dc9f-4396-8d5f-8c081fb06d67	https://git.kernel.org/stable/c/2f944e6255c2fc1c9bd9ee32f6b14ee0b2a51eb5
416baaa9-dc9f-4396-8d5f-8c081fb06d67	https://git.kernel.org/stable/c/557418e1704605a81c9e26732449f71b1d40ba1e
416baaa9-dc9f-4396-8d5f-8c081fb06d67	https://git.kernel.org/stable/c/5a24cedc243ace5ed7c1016f52a7bfc8f5b07815
416baaa9-dc9f-4396-8d5f-8c081fb06d67	https://git.kernel.org/stable/c/6d7c6ae1efb1ff68bc01d79d94fdf0388f86cdd8
416baaa9-dc9f-4396-8d5f-8c081fb06d67	https://git.kernel.org/stable/c/79510414a7626317f13cc9073244ab7a8deb3192
416baaa9-dc9f-4396-8d5f-8c081fb06d67	https://git.kernel.org/stable/c/84398204c5df5aaf89453056cf0647cda9664d2b
416baaa9-dc9f-4396-8d5f-8c081fb06d67	https://git.kernel.org/stable/c/b040b71d99ee5e17bb7a743dc01cbfcae8908ce1
416baaa9-dc9f-4396-8d5f-8c081fb06d67	https://git.kernel.org/stable/c/bf090f4fe935294361eabd9dc5a949fdd77d3d1b
suse_bugzilla	http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-47712	https://bugzilla.suse.com/show_bug.cgi?id=1232017
suse_bugzilla	https://git.kernel.org/pub/scm/linux/security/vulns.git/plain/cve/published/2024/CVE-2024-47712.mbox	https://bugzilla.suse.com/show_bug.cgi?id=1232017
suse_bugzilla	https://git.kernel.org/stable/c/557418e1704605a81c9e26732449f71b1d40ba1e	https://bugzilla.suse.com/show_bug.cgi?id=1232017
suse_bugzilla	https://git.kernel.org/stable/c/bf090f4fe935294361eabd9dc5a949fdd77d3d1b	https://bugzilla.suse.com/show_bug.cgi?id=1232017
suse_bugzilla	https://git.kernel.org/stable/c/b040b71d99ee5e17bb7a743dc01cbfcae8908ce1	https://bugzilla.suse.com/show_bug.cgi?id=1232017
suse_bugzilla	https://git.kernel.org/stable/c/84398204c5df5aaf89453056cf0647cda9664d2b	https://bugzilla.suse.com/show_bug.cgi?id=1232017
suse_bugzilla	https://git.kernel.org/stable/c/2f944e6255c2fc1c9bd9ee32f6b14ee0b2a51eb5	https://bugzilla.suse.com/show_bug.cgi?id=1232017
suse_bugzilla	https://git.kernel.org/stable/c/79510414a7626317f13cc9073244ab7a8deb3192	https://bugzilla.suse.com/show_bug.cgi?id=1232017
suse_bugzilla	https://git.kernel.org/stable/c/6d7c6ae1efb1ff68bc01d79d94fdf0388f86cdd8	https://bugzilla.suse.com/show_bug.cgi?id=1232017
suse_bugzilla	https://www.cve.org/CVERecord?id=CVE-2024-47712	https://bugzilla.suse.com/show_bug.cgi?id=1232017
suse_bugzilla	https://bugzilla.redhat.com/show_bug.cgi?id=2320243	https://bugzilla.suse.com/show_bug.cgi?id=1232017
redhat_bugzilla	https://lore.kernel.org/linux-cve-announce/2024102118-CVE-2024-47712-13c2@gregkh/T	https://bugzilla.redhat.com/show_bug.cgi?id=2320243
debian		https://security-tracker.debian.org/tracker/CVE-2024-47712
mageia		http://advisories.mageia.org/MGASA-2024-0345.html

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

详情(点击展开)

影响的包	修复版本	修复补丁	问题引入补丁	来源
		https://git.kernel.org/stable/c/2f944e6255c2fc1c9bd9ee32f6b14ee0b2a51eb5		nvd
		https://git.kernel.org/stable/c/557418e1704605a81c9e26732449f71b1d40ba1e		nvd
		https://git.kernel.org/stable/c/6d7c6ae1efb1ff68bc01d79d94fdf0388f86cdd8		nvd
		https://git.kernel.org/stable/c/79510414a7626317f13cc9073244ab7a8deb3192		nvd
		https://git.kernel.org/stable/c/84398204c5df5aaf89453056cf0647cda9664d2b		nvd
		https://git.kernel.org/stable/c/b040b71d99ee5e17bb7a743dc01cbfcae8908ce1		nvd
		https://git.kernel.org/stable/c/bf090f4fe935294361eabd9dc5a949fdd77d3d1b		nvd

二、漏洞分析结构反馈
影响性分析说明：
Reserved.
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-22.03-LTS-SP3(5.10.0):受影响
2.openEuler-22.03-LTS-SP4(5.10.0):受影响
3.openEuler-24.03-LTS(6.6.0):受影响
4.openEuler-20.03-LTS-SP4(4.19.90):不受影响
5.master(6.6.0):不受影响
6.openEuler-24.03-LTS-Next(6.6.0):不受影响
7.openEuler-24.03-LTS-SP1(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-24.03-LTS(6.6.0):正常修复
2.openEuler-22.03-LTS-SP3(5.10.0):不修复-超出修复范围
3.openEuler-22.03-LTS-SP4(5.10.0):不修复-超出修复范围
4.master(6.6.0):不受影响-漏洞代码不能被攻击者触发
5.openEuler-24.03-LTS-Next(6.6.0):不受影响-漏洞代码不能被攻击者触发
6.openEuler-20.03-LTS-SP4(4.19.90):不受影响-漏洞代码不存在
7.openEuler-24.03-LTS-SP1(6.6.0):不受影响-漏洞代码不存在

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):

修复是否涉及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):

-----------------------------------------------------------------------
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-47712

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

wifi: wilc1000: fix potential RCU dereference issue in wilc_parse_join_bss_param

In the wilc_parse_join_bss_param function, the TSF field of the ies
structure is accessed after the RCU read-side critical section is
unlocked. According to RCU usage rules, this is illegal. Reusing this
pointer can lead to unpredictable behavior, including accessing memory
that has been updated or causing use-after-free issues.

This possible bug was identified using a static analysis tool developed
by myself, specifically designed to detect RCU-related issues.

To address this, the TSF value is now stored in a local variable
ies_tsf before the RCU lock is released. The param->tsf_lo field is
then assigned using this local variable, ensuring that the TSF value is
safely accessed.

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

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:否