CVE-2023-52510

一、漏洞信息
漏洞编号：CVE-2023-52510
漏洞归属组件：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
CVSS V2.0分值：
BaseScore：0.0 Low
Vector：CVSS：2.0/
漏洞简述：
In the Linux kernel, the following vulnerability has been resolved:ieee802154: ca8210: Fix a potential UAF in ca8210_probeIf of_clk_add_provider() fails in ca8210_register_ext_clock(),it calls clk_unregister() to release priv->clk and returns anerror. However, the caller ca8210_probe() then calls ca8210_remove(),where priv->clk is freed again in ca8210_unregister_ext_clock(). Inthis case, a use-after-free may happen in the second time we callclk_unregister().Fix this by removing the first clk_unregister(). Also, priv->clk couldbe an error code on failure of clk_register_fixed_rate(). UseIS_ERR_OR_NULL to catch this case in ca8210_unregister_ext_clock().
漏洞公开时间：2024-03-03 06:15:47
漏洞创建时间：2024-03-03 06:29:48
漏洞详情参考链接：
https://nvd.nist.gov/vuln/detail/CVE-2023-52510

更多参考(点击展开)

参考来源	参考链接	来源链接
416baaa9-dc9f-4396-8d5f-8c081fb06d67	https://git.kernel.org/stable/c/217efe32a45249eb07dcd7197e8403de98345e66
416baaa9-dc9f-4396-8d5f-8c081fb06d67	https://git.kernel.org/stable/c/28b68cba378e3e50a4082b65f262bc4f2c7c2add
416baaa9-dc9f-4396-8d5f-8c081fb06d67	https://git.kernel.org/stable/c/55e06850c7894f00d41b767c5f5665459f83f58f
416baaa9-dc9f-4396-8d5f-8c081fb06d67	https://git.kernel.org/stable/c/84c6aa0ae5c4dc121f9996bb8fed46c80909d80e
416baaa9-dc9f-4396-8d5f-8c081fb06d67	https://git.kernel.org/stable/c/85c2857ef90041f567ce98722c1c342c4d31f4bc
416baaa9-dc9f-4396-8d5f-8c081fb06d67	https://git.kernel.org/stable/c/becf5c147198f4345243c5df0c4f035415491640
416baaa9-dc9f-4396-8d5f-8c081fb06d67	https://git.kernel.org/stable/c/cdb46be93c1f7bbf2c4649e9fc5fb147cfb5245d
416baaa9-dc9f-4396-8d5f-8c081fb06d67	https://git.kernel.org/stable/c/f990874b1c98fe8e57ee9385669f501822979258
suse_bugzilla	http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-52510	https://bugzilla.suse.com/show_bug.cgi?id=1220898
suse_bugzilla	https://git.kernel.org/stable/c/f990874b1c98fe8e57ee9385669f501822979258	https://bugzilla.suse.com/show_bug.cgi?id=1220898
suse_bugzilla	https://www.cve.org/CVERecord?id=CVE-2023-52510	https://bugzilla.suse.com/show_bug.cgi?id=1220898
suse_bugzilla	https://git.kernel.org/stable/c/217efe32a45249eb07dcd7197e8403de98345e66	https://bugzilla.suse.com/show_bug.cgi?id=1220898
suse_bugzilla	https://git.kernel.org/stable/c/28b68cba378e3e50a4082b65f262bc4f2c7c2add	https://bugzilla.suse.com/show_bug.cgi?id=1220898
suse_bugzilla	https://git.kernel.org/stable/c/55e06850c7894f00d41b767c5f5665459f83f58f	https://bugzilla.suse.com/show_bug.cgi?id=1220898
suse_bugzilla	https://git.kernel.org/stable/c/84c6aa0ae5c4dc121f9996bb8fed46c80909d80e	https://bugzilla.suse.com/show_bug.cgi?id=1220898
suse_bugzilla	https://git.kernel.org/stable/c/85c2857ef90041f567ce98722c1c342c4d31f4bc	https://bugzilla.suse.com/show_bug.cgi?id=1220898
suse_bugzilla	https://git.kernel.org/stable/c/becf5c147198f4345243c5df0c4f035415491640	https://bugzilla.suse.com/show_bug.cgi?id=1220898
suse_bugzilla	https://git.kernel.org/stable/c/cdb46be93c1f7bbf2c4649e9fc5fb147cfb5245d	https://bugzilla.suse.com/show_bug.cgi?id=1220898
redhat_bugzilla	https://lore.kernel.org/linux-cve-announce/2024030250-CVE-2023-52510-6f8a@gregkh/T/#u	https://bugzilla.redhat.com/show_bug.cgi?id=2267773
debian		https://security-tracker.debian.org/tracker/CVE-2023-52510
cve_search		https://git.kernel.org/stable/c/28b68cba378e3e50a4082b65f262bc4f2c7c2add
cve_search		https://git.kernel.org/stable/c/cdb46be93c1f7bbf2c4649e9fc5fb147cfb5245d
cve_search		https://git.kernel.org/stable/c/85c2857ef90041f567ce98722c1c342c4d31f4bc
cve_search		https://git.kernel.org/stable/c/55e06850c7894f00d41b767c5f5665459f83f58f
cve_search		https://git.kernel.org/stable/c/84c6aa0ae5c4dc121f9996bb8fed46c80909d80e
cve_search		https://git.kernel.org/stable/c/217efe32a45249eb07dcd7197e8403de98345e66
cve_search		https://git.kernel.org/stable/c/becf5c147198f4345243c5df0c4f035415491640
cve_search		https://git.kernel.org/stable/c/f990874b1c98fe8e57ee9385669f501822979258
ubuntu	https://git.kernel.org/linus/f990874b1c98fe8e57ee9385669f501822979258 (6.6-rc6)	https://ubuntu.com/security/CVE-2023-52510
ubuntu	https://www.cve.org/CVERecord?id=CVE-2023-52510	https://ubuntu.com/security/CVE-2023-52510
ubuntu	https://nvd.nist.gov/vuln/detail/CVE-2023-52510	https://ubuntu.com/security/CVE-2023-52510
ubuntu	https://launchpad.net/bugs/cve/CVE-2023-52510	https://ubuntu.com/security/CVE-2023-52510
ubuntu	https://security-tracker.debian.org/tracker/CVE-2023-52510	https://ubuntu.com/security/CVE-2023-52510
ubuntu	https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-52510	https://ubuntu.com/security/CVE-2023-52510

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

详情(点击展开)

影响的包	修复版本	修复补丁	问题引入补丁	来源
linux		https://git.kernel.org/linus/f990874b1c98fe8e57ee9385669f501822979258	https://git.kernel.org/linus/ded845a781a578dfb0b5b2c138e5a067aa3b1242	ubuntu

二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:ieee802154: ca8210: Fix a potential UAF in ca8210_probeIf of_clk_add_provider() fails in ca8210_register_ext_clock(),it calls clk_unregister() to release priv->clk and returns anerror. However, the caller ca8210_probe() then calls ca8210_remove(),where priv->clk is freed again in ca8210_unregister_ext_clock(). Inthis case, a use-after-free may happen in the second time we callclk_unregister().Fix this by removing the first clk_unregister(). Also, priv->clk couldbe an error code on failure of clk_register_fixed_rate(). UseIS_ERR_OR_NULL to catch this case in ca8210_unregister_ext_clock().
openEuler评分：
6.7
Vector：CVSS：2.0/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
受影响版本排查(受影响/不受影响)：
1.openEuler-20.03-LTS-SP1(4.19.90):受影响
2.openEuler-20.03-LTS-SP4(4.19.90):受影响
3.openEuler-22.03-LTS(5.10.0):受影响
4.openEuler-22.03-LTS-SP1(5.10.0):受影响
5.openEuler-22.03-LTS-SP2(5.10.0):受影响
6.openEuler-22.03-LTS-SP3(5.10.0):受影响
7.master(6.1.0):不受影响
8.openEuler-22.03-LTS-Next(5.10.0):不受影响
9.openEuler-24.03-LTS:不受影响
10.openEuler-24.03-LTS-Next:不受影响

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

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

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 ,@gatieme ,@jiaoff ,@guohaocs2c ,@hanjun-guo ,@woqidaideshi ,@newbeats ,@zhangyi089 ,@colyli ,@thundertown ,@htforge ,@chiqijun ,@lengchao ,@zhujianwei001 ,@kylin-mayukun ,@wangxiongfeng ,@wkfxxx ,@SuperSix173 ,@jentlestea ,@oskernel0719 
**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):

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

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

参考网址	关联pr	状态	补丁链接
https://nvd.nist.gov/vuln/detail/CVE-2023-52510	None	None	https://git.kernel.org/stable/c/55e06850c7894f00d41b767c5f5665459f83f58f https://git.kernel.org/stable/c/84c6aa0ae5c4dc121f9996bb8fed46c80909d80e https://git.kernel.org/stable/c/85c2857ef90041f567ce98722c1c342c4d31f4bc https://git.kernel.org/stable/c/217efe32a45249eb07dcd7197e8403de98345e66 https://git.kernel.org/stable/c/becf5c147198f4345243c5df0c4f035415491640 https://git.kernel.org/stable/c/f990874b1c98fe8e57ee9385669f501822979258 https://git.kernel.org/stable/c/cdb46be93c1f7bbf2c4649e9fc5fb147cfb5245d https://git.kernel.org/stable/c/28b68cba378e3e50a4082b65f262bc4f2c7c2add
https://ubuntu.com/security/CVE-2023-52510	None	None	https://discourse.ubuntu.com/c/ubuntu-pro
https://www.opencve.io/cve/CVE-2023-52510	None	None	https://git.kernel.org/stable/c/55e06850c7894f00d41b767c5f5665459f83f58f https://git.kernel.org/stable/c/84c6aa0ae5c4dc121f9996bb8fed46c80909d80e https://git.kernel.org/stable/c/85c2857ef90041f567ce98722c1c342c4d31f4bc https://git.kernel.org/stable/c/217efe32a45249eb07dcd7197e8403de98345e66 https://git.kernel.org/stable/c/becf5c147198f4345243c5df0c4f035415491640 https://git.kernel.org/stable/c/f990874b1c98fe8e57ee9385669f501822979258 https://git.kernel.org/stable/c/cdb46be93c1f7bbf2c4649e9fc5fb147cfb5245d https://git.kernel.org/stable/c/28b68cba378e3e50a4082b65f262bc4f2c7c2add
https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2023-52510
https://security-tracker.debian.org/tracker/CVE-2023-52510

说明：补丁链接仅供初步排查参考，实际可用性请人工再次确认，补丁下载验证可使用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-2023-52510

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

ieee802154: ca8210: Fix a potential UAF in ca8210_probe

If of_clk_add_provider() fails in ca8210_register_ext_clock(),
it calls clk_unregister() to release priv->clk and returns an
error. However, the caller ca8210_probe() then calls ca8210_remove(),
where priv->clk is freed again in ca8210_unregister_ext_clock(). In
this case, a use-after-free may happen in the second time we call
clk_unregister().

Fix this by removing the first clk_unregister(). Also, priv->clk could
be an error code on failure of clk_register_fixed_rate(). Use
IS_ERR_OR_NULL to catch this case in ca8210_unregister_ext_clock().

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

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

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

@CTC-XiboWang 经过 cve-manager 解析, 已分析的内容如下表所示:
| 状态  | 需分析 | 内容 |
|:--:|:--:|---------|
|已分析|1.影响性分析说明|In the Linux kernel, the following vulnerability has been resolved:ieee802154: ca8210: Fix a potential UAF in ca8210_probeIf of_clk_add_provider() fails in ca8210_register_ext_clock(),it calls clk_unregister() to release priv->clk and returns anerror. However, the caller ca8210_probe() then calls ca8210_remove(),where priv->clk is freed again in ca8210_unregister_ext_clock(). Inthis case, a use-after-free may happen in the second time we callclk_unregister().Fix this by removing the first clk_unregister(). Also, priv->clk couldbe an error code on failure of clk_register_fixed_rate(). UseIS_ERR_OR_NULL to catch this case in ca8210_unregister_ext_clock().|
|已分析|2.openEulerScore|6|
|已分析|3.openEulerVector|AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:H|
|已分析|4.受影响版本排查|openEuler-20.03-LTS-SP1:受影响,openEuler-20.03-LTS-SP4:受影响,openEuler-22.03-LTS:受影响,openEuler-22.03-LTS-SP1:受影响,openEuler-22.03-LTS-SP2:受影响,openEuler-22.03-LTS-SP3:受影响,openEuler-22.03-LTS-Next:受影响,master:不受影响,openEuler-24.03-LTS:不受影响|
|已分析|5.修复是否涉及abi变化|openEuler-20.03-LTS-SP1:否,openEuler-20.03-LTS-SP4:否,openEuler-22.03-LTS:否,openEuler-22.03-LTS-SP1:否,openEuler-22.03-LTS-SP2:否,openEuler-22.03-LTS-SP3:否,master:否,openEuler-22.03-LTS-Next:否,openEuler-24.03-LTS:否|

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

CVE-2023-52510

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

ieee802154: ca8210: Fix a potential UAF in ca8210_probe

If of_clk_add_provider() fails in ca8210_register_ext_clock(),
it calls clk_unregister() to release priv->clk and returns an
error. However, the caller ca8210_probe() then calls ca8210_remove(),
where priv->clk is freed again in ca8210_unregister_ext_clock(). In
this case, a use-after-free may happen in the second time we call
clk_unregister().

Fix this by removing the first clk_unregister(). Also, priv->clk could
be an error code on failure of clk_register_fixed_rate(). Use
IS_ERR_OR_NULL to catch this case in ca8210_unregister_ext_clock().

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

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

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

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

@CTC-XiboWang 经过 cve-manager 解析, 已分析的内容如下表所示:
| 状态  | 需分析 | 内容 |
|:--:|:--:|---------|
|已分析|1.影响性分析说明|In the Linux kernel, the following vulnerability has been resolved:ieee802154: ca8210: Fix a potential UAF in ca8210_probeIf of_clk_add_provider() fails in ca8210_register_ext_clock(),it calls clk_unregister() to release priv->clk and returns anerror. However, the caller ca8210_probe() then calls ca8210_remove(),where priv->clk is freed again in ca8210_unregister_ext_clock(). Inthis case, a use-after-free may happen in the second time we callclk_unregister().Fix this by removing the first clk_unregister(). Also, priv->clk couldbe an error code on failure of clk_register_fixed_rate(). UseIS_ERR_OR_NULL to catch this case in ca8210_unregister_ext_clock().|
|已分析|2.openEulerScore|6.7|
|已分析|3.openEulerVector|AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H|
|已分析|4.受影响版本排查|openEuler-20.03-LTS-SP1:受影响,openEuler-20.03-LTS-SP4:受影响,openEuler-22.03-LTS:受影响,openEuler-22.03-LTS-SP1:受影响,openEuler-22.03-LTS-SP2:受影响,openEuler-22.03-LTS-SP3:受影响,master:不受影响,openEuler-22.03-LTS-Next:不受影响,openEuler-24.03-LTS:不受影响,openEuler-24.03-LTS-Next:不受影响|
|已分析|5.修复是否涉及abi变化|openEuler-20.03-LTS-SP1:否,openEuler-20.03-LTS-SP4:否,openEuler-22.03-LTS:否,openEuler-22.03-LTS-SP1:否,openEuler-22.03-LTS-SP2:否,openEuler-22.03-LTS-SP3:否,master:否,openEuler-22.03-LTS-Next:否,openEuler-24.03-LTS:否,openEuler-24.03-LTS-Next:否|

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

src-openEuler/kernel

内容风险标识

评论 (19)

src-openEuler/kernel .gitee-modal { width: 500px !important; }

内容风险标识

CVE-2023-52510

评论 (19)

搜索帮助

src-openEuler/kernel